From: "Shawn O. Pearce" <spearce@spearce.org>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org, Martin Waitz <tali@admingilde.org>
Subject: Re: [PATCH 2/4] update-hook: show the contents of the tag message for annotated tags
Date: Tue, 20 Mar 2007 11:36:48 -0400 [thread overview]
Message-ID: <20070320153648.GC1750@spearce.org> (raw)
In-Reply-To: <200703201527.15476.andyparkins@gmail.com>
Andy Parkins <andyparkins@gmail.com> wrote:
> On Tuesday 2007 March 20 12:41, Martin Waitz wrote:
>
> > > Which is dangerously reliant on the format of the tag object being four
> > > header lines then the message.
> >
> > I think you can split at the blank line after the header.
>
> That's a good idea; I can't think of an efficient way of doing that in shell
> script though. What I need is a
>
> grep --everything-after "^$"
sed -e '1,/^$/d'
Portable too. ;-)
--
Shawn.
prev parent reply other threads:[~2007-03-20 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 10:58 [PATCH 2/4] update-hook: show the contents of the tag message for annotated tags Andy Parkins
2007-03-20 12:41 ` Martin Waitz
2007-03-20 15:27 ` Andy Parkins
2007-03-20 15:36 ` Shawn O. Pearce [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=20070320153648.GC1750@spearce.org \
--to=spearce@spearce.org \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=tali@admingilde.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;
as well as URLs for NNTP newsgroup(s).