From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] The "table-of-contents" in the update hook script should match the body
Date: Thu, 15 Feb 2007 10:15:46 +0000 [thread overview]
Message-ID: <200702151015.47828.andyparkins@gmail.com> (raw)
In-Reply-To: <7vy7n0r87y.fsf@assigned-by-dhcp.cox.net>
On Wednesday 2007 February 14 16:53, Junio C Hamano wrote:
> > -newrev_type=$(git-cat-file -t "$newrev")
> > +newrev_type=$(git-cat-file -t $newrev)
> >
> > case "$refname","$newrev_type" in
> > refs/tags/*,commit)
>
> I do not think this hunk is related...
Oops; yes you're right. I was having trouble with git-cvsserver calling the
update hook; and that was the fix. However, it's nothing to do with that
patch - and I suspect that that fix should more properly be in git-cvsserver.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
prev parent reply other threads:[~2007-02-15 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 11:20 [PATCH] The "table-of-contents" in the update hook script should match the body Andy Parkins
2007-02-14 16:53 ` Junio C Hamano
2007-02-15 10:15 ` Andy Parkins [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=200702151015.47828.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).