On 9/7/2014 17:10, Will Parsons wrote:
I have to admit that I *hate* to mistype a commit message and have it
frozen for all time. Using an editor just seems so much easier...
Fossil lets you edit commit messages. In true Fossil fashion, the old
message isn't overwritten, just *overridden*, so someone can still dig
up your errors, but at least they don't show up by default in the
timeline any more.
I'll put in my vote for always using $EDITOR, by the way.
Sometimes one of my commit messages actually stretches to the point of
needing paragraphs, either because the problem it fixes is particularly
complex or because the solution/feature is.
That brings up a Fossil nit: the timeline compresses whitespace in
commit messages, so you can't see paragraph breaks without digging down
into the individual checkin. I wish it would not collapse double
newlines. I'm fine with it joining lines separated by only a single
newline, so that my max-72-column wide commit messages fill the window
width in the browser, but if I put in a double newline, fossil ui should
show a paragraph break.
I will say that I treat a multi-paragraph commit message as a warning
sign. I ask myself if the commit message is getting long because either
the checkin is overly complex, or because I don't really understand
what's going on. Sometimes I can simplify or clarify the change or its
checkin comment, but not always. Sometimes the act of composing such a
long checkin comment clues me into a better fix, which I would never
have discovered if I didn't try to thoroughly explain the "whys" of each
change.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
