From: "Keller, Jacob E" <jacob.e.keller@intel.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>,
"varuag.chhabra@gmail.com" <varuag.chhabra@gmail.com>
Subject: Re: Git tag: pre-receive hook issue
Date: Mon, 20 Jul 2015 16:02:45 +0000 [thread overview]
Message-ID: <1437408165.11638.3.camel@intel.com> (raw)
In-Reply-To: <CAGDgvc08ZMdKH-6FdtYWXCBbiX=UYdKTTKVtEF65J+jW5mDYCA@mail.gmail.com>
On Mon, 2015-07-20 at 13:13 +0530, Gaurav Chhabra wrote:
> Hi Jake,
>
> Thanks about the refs/tags check. I’m aware about this. Junio also
> explained it in one of his replies. I was actually confused why my
> current code was working in past for few of the annotated tags.
> Anyways, now that I have clarity about the mistake in the code, I
> guess, I’ll figure it out myself.
>
> @Junio: Thanks a lot for your detailed explanation about the ‘behind
> the scenes’ activity during a push process. That was definitely
> helpful and will help me in future too.
>
> @Jake: Thanks for your help and your patience in explaining things.
>
No problem. I'm also not certain why it would have worked in some
cases, so that is definitely confusing, but at least you can get it
sorted to do what you intend. Best of luck!
Regards,
Jake
next prev parent reply other threads:[~2015-07-20 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 18:58 Git tag: pre-receive hook issue Garbageyard
2015-07-17 19:30 ` Junio C Hamano
2015-07-18 4:00 ` Jacob Keller
2015-07-18 20:08 ` Gaurav Chhabra
2015-07-18 21:19 ` Junio C Hamano
2015-07-18 22:22 ` Jacob Keller
2015-07-19 7:55 ` Gaurav Chhabra
2015-07-19 8:38 ` Jacob Keller
2015-07-19 10:13 ` Gaurav Chhabra
2015-07-19 23:35 ` Jacob Keller
2015-07-20 7:43 ` Gaurav Chhabra
2015-07-20 16:02 ` Keller, Jacob E [this message]
2015-07-22 19:46 ` Jakub Narębski
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=1437408165.11638.3.camel@intel.com \
--to=jacob.e.keller@intel.com \
--cc=git@vger.kernel.org \
--cc=varuag.chhabra@gmail.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.
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).