git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Lyons, Roy" <Roy.Lyons@cmegroup.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: deletion of branch seems to modify tag as well?
Date: Wed, 5 Jun 2013 11:51:24 -0400	[thread overview]
Message-ID: <20130605155124.GB8664@sigill.intra.peff.net> (raw)
In-Reply-To: <58EAA08AF8232344ADDB2E31D4996BFD39F271BA@SMRPEXCHIDAG2.prod.ad.merc.chicago.cme.com>

On Wed, Jun 05, 2013 at 03:26:18PM +0000, Lyons, Roy wrote:

> $ git push origin :ABRANCHNAME
> remote: Firing Pre - receive hook
> remote:
> remote:
> remote: Firing Post receive hook
> remote:
> remote: Branch is ABRANCHNAME -- not creating Trigger file since this is not _int branch
> remote: error: Trying to write ref refs/tags/ABRANCHNAME!SN-BL-20130605_100513_04363 with nonexistent object 0000000000000000000000000000000000000000
> remote: fatal: refs/tags/ABRANCHNAME!SN-BL-20130605_100513_04363: cannot update the ref
> To ssh://git@ourgitserver/repositoryname.git
> - [deleted] ABRANCHNAME
> 
> I would not expect this behavior.  Is git attempting to modify the
> tags associated to the HEAD commit on the branch in addition to the
> branch?   If so, I would like to consider this a bug report...

I do not think git is doing anything of the sort. The output you see
above comes from custom hooks on the server. We cannot say for certain
without seeing the hook's code, but it looks like the post-receive hook
is trying to create a tag to point to the tip of every push, but whoever
wrote the hook did not take into account branch deletions (and the fact
that you cannot create a tag pointing at a deletion).

-Peff

  reply	other threads:[~2013-06-05 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 15:26 deletion of branch seems to modify tag as well? Lyons, Roy
2013-06-05 15:51 ` Jeff King [this message]
2013-06-05 15:53   ` Lyons, Roy

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=20130605155124.GB8664@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Roy.Lyons@cmegroup.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).