I demand that Adam D. Barratt may or may not have written... [snip] > On Mon, 2008-01-28 at 15:00 +0000, Darren Salt wrote: >> I see the same bug here, or at least the results of this bug. "hg log" and >> the hgweb summary view show only the first line of each, which can be >> misleading as to the actual content of the changeset.
> Does hg also follow a similar convention to git? (i.e. summary\n \ndetail) > Or is it simply detail\ndetail\ndetail\n with the first line of detail > being used as a summary by "hg log"? The latter, although "hg import", when given an RFC2822-compliant message, will use the subject header (which, unfortunately, it doesn't unwrap) and the body text as the commit message. >> Here are a few example changesets: >> Multi-line single item: >> http://hg.debian.org/hg/xine-lib/pkg/xine-lib-1.2-deb?cmd=changeset;node=66 > Would unfolding the changelog entry to a single line work here, or is > there still a limit to the number of characters that will be displayed? Unwrapping that would work; I'm not aware of any upper limit. >> Multi-line multiple items: >> http://hg.debian.org/hg/xine-lib/pkg/xine-lib-1.2-deb?cmd=changeset;node=57 > The answer to this question will probably be largely informed by the > previous two :) but would my earlier suggestion of creating an initial > message which the committer could then edit work in this case? I see no reason why that wouldn't work. -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | Let's keep the pound sterling Stop that! It's silly! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
