From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Beller <sbeller@google.com>,
Philip Oakley <philipoakley@iee.org>,
Christian Couder <christian.couder@gmail.com>,
git <git@vger.kernel.org>, Ben Peart <Ben.Peart@microsoft.com>,
Jonathan Tan <jonathantanmy@google.com>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Mike Hommey <mh@glandium.org>,
Lars Schneider <larsxschneider@gmail.com>,
Eric Wong <e@80x24.org>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: On the nature of cover letters [WAS Re: [PATCH 0/6] Create Git/Packet.pm]
Date: Thu, 2 Nov 2017 04:01:12 -0400 [thread overview]
Message-ID: <20171102080111.edh5wqyklkoqkvlg@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqh8udqfxe.fsf@gitster.mtv.corp.google.com>
On Thu, Nov 02, 2017 at 04:48:45PM +0900, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > If the clutter is too much, it could also go into a git-notes ref
> > (that's not already implemented, but it seems like it would be pretty
> > easy to teach "git am" to do that).
>
> FWIW, that is what I use a notes ref "amlog" for.
Right, I completely forgot that you were already doing that. So jumping
to the thread for a commit is basically:
$browser $(git notes --ref=amlog show $commit |
perl -pe 's{Message-Id: <(.*)>}{https://public-inbox.org/git/$1/t}')
(Or whichever archive you prefer to use). Thanks for the reminder.
-Peff
next prev parent reply other threads:[~2017-11-02 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 18:29 On the nature of cover letters [WAS Re: [PATCH 0/6] Create Git/Packet.pm] Stefan Beller
2017-11-01 7:14 ` Jeff King
2017-11-01 16:42 ` Stefan Beller
2017-11-01 22:31 ` Stefan Beller
2017-11-02 7:22 ` Jeff King
2017-11-02 7:48 ` Junio C Hamano
2017-11-02 8:01 ` Jeff King [this message]
2017-11-02 18:03 ` Stefan Beller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171102080111.edh5wqyklkoqkvlg@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Ben.Peart@microsoft.com \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=larsxschneider@gmail.com \
--cc=mh@glandium.org \
--cc=pclouds@gmail.com \
--cc=philipoakley@iee.org \
--cc=sbeller@google.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).