From: "Shawn O. Pearce" <spearce@spearce.org>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/4] update-hook: parse the tag header in preparation to use the tag type
Date: Tue, 20 Mar 2007 10:38:44 -0400 [thread overview]
Message-ID: <20070320143844.GA1750@spearce.org> (raw)
In-Reply-To: <200703201058.42753.andyparkins@gmail.com>
Andy Parkins <andyparkins@gmail.com> wrote:
> The tag header is parsed with a while loop and read command. I'm not
> entirely sure how portable it is, as it had to use the following unusual
> heredoc format:
>
> while read field value
> do
> # ..
> done <<< "$(some command)"
To bad you can't use for-each-ref. ;-)
The problem of course is the update hook is running before a ref
is created to point at the tag. If you used post-receive hook
on the other hand... Oh, right, that has its own problems too!
--
Shawn.
next prev parent reply other threads:[~2007-03-20 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 10:58 [PATCH 3/4] update-hook: parse the tag header in preparation to use the tag type Andy Parkins
2007-03-20 14:38 ` Shawn O. Pearce [this message]
2007-03-20 15:24 ` Andy Parkins
2007-03-20 15:38 ` Shawn O. Pearce
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=20070320143844.GA1750@spearce.org \
--to=spearce@spearce.org \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.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).