-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 26 Mar 2009 09:24:28 -0400 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. > Probably can't assume we're only interested in commits starting with a bugzilla number, lot of changelog worthy stuff goes in without a bug. Overall I'm not real keen on having rules on commit messages to accommodate the changelog population. IMO it needs to remain a manual process anyhow, and killing lines you're not interested in can be done so easily regardless what $EDITOR you're using. Seems like a bad thing to bind together and something we'd likely struggle constantly with enforcing, after which we'd *still* probably have to review the results manually. Content to just "dd" the uninteresting lines on my end. Cheers, Devan - -- Devan Goodwin <[email protected]> Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknLhZ4ACgkQAyHWaPV9my6fSgCguAXvpbqrDSMe+M6MrV88xhpG +/YAoNJMzxEXAPKGQKGVx3AIBU4K2w0C =gDPv -----END PGP SIGNATURE----- _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
