-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Paul Eggert on 10/10/2007 12:46 AM: > Eric Blake <[EMAIL PROTECTED]> writes: > >> Thanks for doing this. But please remember to separate the summary line >> from the rest of the details in the git commit text. > > This is starting to get a bit off-topic, but I am finding these > from-my-point-of-view oddball restrictions about what goes into > ChangeLog entries fairly onerous. I am just using vc-dwim, which > generates commit text automatically from the ChangeLog. This works in > other projects; why isn't it working here?
Jim, it looks like vc-dwim could use an improvement when targeting git. There are enough places in git tools that expect the summary line to be separated by a blank line from the rest of the commit message; otherwise the entire ChangeLog entry gets concatenated into a single long commit summary, which gets rather hard to read when browsing git history. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHDMNf84KuGfSFAYARAiWuAJwLiEbaMNdJwQjDxMffi4FzJJB0aQCglkY4 CH703NpLSIolk+pHhjXURYc= =YX8Z -----END PGP SIGNATURE-----
