From: Jeff King <peff@peff.net>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] log: respect log.shownotes variable
Date: Thu, 8 Apr 2010 15:16:53 -0400 [thread overview]
Message-ID: <20100408191653.GA14066@sigill.intra.peff.net> (raw)
In-Reply-To: <201004081812.50112.trast@student.ethz.ch>
On Thu, Apr 08, 2010 at 06:12:49PM +0200, Thomas Rast wrote:
> BTW, now that I seem to have a couple of users for those notes: what
> would you like to see in the "short" version (notes/terse)? Improving
For me, the message-id is sufficient. I keep my own local archive of the
git list (because reading old threads in mutt is much nicer than on
gmane), and it is trivial to convert message-id into whatever gmane link
I want for referencing to other people.
-Peff
prev parent reply other threads:[~2010-04-08 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 20:45 [PATCH] log: respect log.shownotes variable Jeff King
2010-04-07 21:53 ` Junio C Hamano
2010-04-08 2:01 ` Michael J Gruber
2010-04-08 7:07 ` Jeff King
2010-04-08 7:05 ` Jeff King
2010-04-08 16:12 ` Thomas Rast
2010-04-08 16:55 ` Junio C Hamano
2010-04-08 19:16 ` Jeff King [this message]
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=20100408191653.GA14066@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@student.ethz.ch \
/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;
as well as URLs for NNTP newsgroup(s).