IcedTea6 1.6 Released!
Andrew John Hughes
gnu_andrew at member.fsf.org
Thu Sep 10 08:30:46 PDT 2009
2009/9/10 Andrew Haley <aph at redhat.com>:
> Andrew John Hughes wrote:
>> As I've mentioned before, it would be nice if we could all standardise
>> on having a 1-line summary in commit messages prior to the ChangeLog,
>> as this is the only line that shows up without verbose output (hg log,
>> shortlog and summary pages on the web view). It would make it easier
>> to select changesets that need to be merged.
> I do not believe this would, in general, be a Good Thing.
> A single summary line can be misleading, so it would be irresponsible
> for someone to merge changesets based on the summary. A missing summary
> line is a clue to someone merging that they really ought to look at the
> whole ChangeLog entry.
> While a single line summary can make sense for some things -- "Merge"
> or "Added tag ..." are good examples -- I'm not sure that this
> particular feature of Mercurial is useful enough to dictate how we
> work. That would be, as they say, the tail wagging the dog.
I'm not suggesting using it as the sole basis for merging; that would
be wrong as you say. But having a summary line better than 2009-08-27
Matthias Klose <doko at ubuntu.com> or 2009-09-09 Andrew Haley
<aph at redhat.com> would mean you can make a more educated guess as to
whether it's worth looking at the entire changeset.
You're always going to get this 1-line summary regardless, it would be
good to have it as something sensible.
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
More information about the distro-pkg-dev