From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Daniele Segato <daniele.bilug@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Git shouldn't allow to push a new branch called HEAD
Date: Mon, 14 Nov 2011 12:22:59 -0800 [thread overview]
Message-ID: <7vbosejvx8.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20111114111659.GC10847@sigill.intra.peff.net> (Jeff King's message of "Mon, 14 Nov 2011 06:16:59 -0500")
Jeff King <peff@peff.net> writes:
> So one solution is to block fetching of remote branches called HEAD
> (which I would be OK with). But another is...
> ... Obviously there's a lot more to it than just tweaking the default fetch
> refspecs. The ref lookup rules need to be changed to take this into
> account. There was some discussion about this over the summer (under the
> subject of possible "1.8.0" changes), but I don't think any work has
> been done.
I would say discussing and ironing out the kinks of the design counts as
work, but I agree nobody was seriously interested in laying out a sensible
transition plan and discussion died out before anything concrete happened.
Regardless of the layout chanage, which probably is a 2.X topic, I think a
good first step would be to start forbidding anything that ends with _?HEAD
as a branch or tag name, on top of Michael's "enforce the refname rules more
vigorously when a ref is created" series.
next prev parent reply other threads:[~2011-11-14 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 11:31 Git shouldn't allow to push a new branch called HEAD Daniele Segato
2011-10-14 11:35 ` Daniele Segato
2011-11-14 9:07 ` Daniele Segato
2011-11-14 10:45 ` Michael Haggerty
2011-11-14 11:16 ` Jeff King
2011-11-14 20:22 ` Junio C Hamano [this message]
2011-11-14 20:26 ` Jeff King
2011-10-14 23:00 ` P Rouleau
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=7vbosejvx8.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=daniele.bilug@gmail.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.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