[combining replies]
Hi,
On Sun, 2006-12-10 at 16:56 -0800, Jamey Sharp wrote:
> Given a change which stretches over multiple lines, debcommit currently
> generates commit messages which look like this:
>
> * Install pkg-config files to /usr/lib/pkgconfig, not
> /usr/share/pkgconfig.
>
> In Git, commit messages follow an email-like convention of using the
> first line like a subject, then leaving a blank line, and then
> optionally writing a more detailed commit message. Ideally, debcommit
> should format its commit messages in the same way. In the particular
> case of a single message, it could default to stripping the * and
> putting the whole message on one line.
The first part is already possible (-s / --strip-message /
DEBCOMMIT_STRIP_MESSAGE); the second wouldn't be difficult to implement.
Is there any limit on the length of the summary line, or could e.g.
* A nice long change to break over multiple lines. Blah blah blah
blah. This should break over three lines. Pad fill pad fill pad
fill blah.
be unfolded to a single line for the summary?
> For the general case, if no
> reasonable way exists to do this systematically, then perhaps debcommit
> should offer an option to supply a subject-like summary of the changes,
> or an option to edit the commit message before committing.
Editing is now possible, via -e/--edit or the [e]dit option of -C /
--confirm but this must be specified per invocation (so you'd need to
always supply it or make a judgement call first).
Would it be useful in the case of a git commit with multiple changes to
create an initial commit message of the form:
<first change unfolded and with leading asterisk stripped>
* First change
* Second change
and then proceed as if --edit had been passed?
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"?
> 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?
> 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?
Regards,
Adam
--
To unsubscribe, send mail to [EMAIL PROTECTED]
