On 12/23/2011 05:19 PM, Jim Meyering wrote: >>> However, I would prefer an adaptive/hybrid solution: if a commit log >>> is composed of two or more paragraphs, keep it in a separate block. >>> Otherwise, merge entries that would otherwise have a date--name--email >>> header identical to the preceding one. > > I am considering making this the default, with no option > to produce the current behavior. > >> That's fine by me, as long as I can also instruct gitlog-to-changelog to >> unconditionally keep separate commit messages (also if just one paragraph >> lond) in separate blocks. You know, "give the user enough rope" etc etc. > > You still have not explained why you would like this mode of operation. > This would require an option, hence justification. > My justification is quite weak: I prefer consistency, so I'd rather have every ChangeLog entry in a separate blocks, rather than having some separate and some clustered. Yes, this is a purely cosmetic consideration.
Anyway, it's not a big deal: the change you are proposing would still be a definite improvement, because it would always ensure correctness (which currently is lacking for multi-paragraph commit messages); I could then patch gitlog-to-changelog myself for the eye-candy, if I really want to. Regards, Stefano
