Jay Asbury

> > Do you see how this should not be an APP setting but a git config value. > > I'm afraid I don't understand what you mean. Either way,...

The problem you are causing is a shadowing of what git does and instead you should work with it and reflect it and use it. Not this check box to...

I would skip default = hardcoded # and default to git config and then allow other strategies. The whole point is we are getting rid of hard coding # throughout....

> > So you have the following cases: > > No you forget additional one comment with spaces. But is is very easy to add/ remove a strategy > >...

Info to help with understanding `git commit --allow-empty` `git -c core.commentString="Comment:" commit --allow-empty` This demonstrates GE inconsistency. Which is where you were going to resolve. Ok I did spot the...

Your strategies are not a bad idea. However, I think they should be internal and should be more like the highlight strategies. Notice how we have default git highlight strategy...

> I think we're talking about different, less important things. The most important question is why GE must skip lines in the comment template. Is it not Git work? Why...

Here is what will happen after your work is done. 1. GE will reliably use comment value to show correct ui and what is a comment line 2. GE will...

Because of your work's strict policy they are hampering you. There may be a review process but I am quite certain your work would be ok with adjusting git config...

> The most important question is why GE must skip lines in the comment Yep it was a poor mans hack for this exact issue. Once you get your work...