On Thu, Mar 26, 2009 at 9:24 AM, Jason Dobies <[email protected]> wrote: >> Problem we have is some of the commit logs are very wordy (which is ok >> but the first sentence isn't descriptive enough) and others are >> so terse that I don't bother including them: fixed unit test. > > Would it be valuable to preface trivial commit messages with something so > they can be filtered out? I don't want to make an overly complicated commit > log process, but if generated change logs become valuable it might be worth > it. > > At the same time, if the commit doesn't start with a BZ number can it just > be automatically considered trivial? One could make the argument that any > "changelog-worthy" work should have a BZ assigned to it.
Basically if the patch pops up an editor with the automatic changelog, I'd be happy with editing it before proceeding. I currently do that today. I do a git log --pretty=oneline then remove trivial ones like 'fixed unit tests' but I leave things like 'refactored Action blah blah blah' In theory bz would be required. I guess that would keep the changelogs to the most important messages. jesus _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
