Credibility? Eternalize? What? Look - I'm just a FOSS coder and I don't care how "professional" or whatever I come across. What I do care about is an /honest/ track record that can be seen in my github profile, amongst other things. I would like to help out in other projects as well, eventually, and I want to be able to offer an honest, cohesive picture of how past efforts went about. That's why I showed you what I did for RedBean - to give you a direct view into how it went down in another example. If I propose help to other projects, I don't think they would care much about how "professional" I am, but they would very much appreciate an honest picture of the process.

This may seem like a fine point (and I suppose both sides look equally silly in standing up for something that may appear minor to outsiders) but just as you have to stand up for your history, I have to stand up for mine. And I'm willing to do that. I have told you, rather clearly, that it is important to me to have it this way and that it is your choice to weigh the options. I consider it a small price to pay, particularly since many of the technical issues noted can be solved, sometimes with something as simple as a '-w'. More importantly though, I consider the price you would have to pay smaller than the one I'm paying.

I understand that my efforts are appreciated by you and so far, I was happy with how the process went, even if I had to make some compromises to points that I originally didn't think were debatable. But I think it's not unreasonable of me to make one or two smaller requirements myself.

Anyways, I'm getting a sense that this is really mostly about commit /messages/. Well alright then. What about if I simply rename those commits? Would be a bit of rebasing, but from my count, there's only about 15 commits that lack a good commit message. Would that be an agreeable compromise?