From: Paul Mackerras <paulus@samba.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Erik Mouw <erik@harddisk-recovery.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Linux v2.6.12-rc6
Date: Wed, 8 Jun 2005 12:08:38 +1000 [thread overview]
Message-ID: <17062.21286.601768.751853@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506070820170.2286@ppc970.osdl.org>
Linus Torvalds writes:
> The merge message that goes along with that shortlog entry is
>
> Author: Linus Torvalds <torvalds@ppc970.osdl.org>
> Date: Sat Jun 4 08:18:39 2005 -0700
>
> Automatic merge of 'misc-fixes' branch from
>
> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6
>
> which is pretty readable in the long format, but causes the shortlog to
> pick up just the partial (largely uninteresing) first line.
This also affects gitk, which takes the first line of the commit
message as the headline. I could make gitk take the first paragraph
(i.e. until the first blank line) as the headline but even that
wouldn't help since you put a blank line between the "Automatic merge"
line and the actual URL. Could you leave out that blank line in
future, or do you have a better suggestion?
Paul.
next prev parent reply other threads:[~2005-06-08 2:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 18:08 Linus Torvalds
2005-06-06 19:26 ` Pavel Machek
2005-06-06 19:54 ` Jeff Garzik
2005-06-06 20:05 ` Pavel Machek
2005-06-06 21:11 ` Linus Torvalds
2005-06-06 21:54 ` Bill Davidsen
2005-06-06 20:12 ` Linus Torvalds
2005-06-06 20:14 ` Pavel Machek
2005-06-06 21:13 ` Linus Torvalds
2005-06-06 21:18 ` Pavel Machek
2005-06-06 21:36 ` Linus Torvalds
2005-06-06 21:41 ` Pavel Machek
2005-06-06 21:53 ` Linus Torvalds
2005-06-06 21:57 ` Jesper Juhl
2005-06-06 22:07 ` Russell King
2005-06-07 9:11 ` Johannes Stezenbach
2005-06-08 11:15 ` Johannes Stezenbach
2005-06-08 11:23 ` Brice Goglin
2005-06-08 11:37 ` Johannes Stezenbach
2005-06-17 17:48 ` Bill Davidsen
2005-06-18 13:57 ` Johannes Stezenbach
2005-06-18 17:10 ` Johannes Stezenbach
2005-06-07 13:05 ` Erik Mouw
2005-06-07 15:28 ` Linus Torvalds
2005-06-07 17:11 ` Erik Mouw
2005-06-07 17:28 ` Linus Torvalds
2005-06-08 2:08 ` Paul Mackerras [this message]
2005-06-08 17:11 ` Linus Torvalds
2005-06-08 16:20 ` Nicolas Pitre
2005-06-07 18:47 ` Jean Delvare
2005-06-09 8:10 ` Greg KH
2005-06-09 15:52 ` Jean Delvare
2005-06-09 16:32 ` Greg KH
2005-06-08 13:37 ` segfaults suddenly appearing Jakob Oestergaard
2005-06-07 6:11 Linux v2.6.12-rc6 Voluspa
2005-06-07 6:18 ` Ingo Molnar
2005-06-07 6:37 ` Voluspa
2005-06-07 7:06 ` Grant Coady
2005-06-07 7:44 ` Dave Airlie
2005-06-07 8:45 ` Voluspa
2005-06-07 8:19 ` Matthias Andree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17062.21286.601768.751853@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=erik@harddisk-recovery.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®