Git ticket / issue tracking ERA: Git shouldn't allow to push a new branch called HEAD
- From
- Daniele Segato <daniele.bilug@gmail.com>
- Date
- Nov 22, 2011, 14:04 UTC
- Message-ID
- <1321970646.3289.19.camel@mastroc3.mobc3.local>
On Mon, 2011-11-14 at 15:26 -0500, Jeff King wrote: On Mon, Nov 14, 2011 at 12:22:59PM -0800, Junio C Hamano wrote:
> > > 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.
> > Yeah, I should have said "...has been done since then". > > > 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. > > Agreed. Changing the layout is a long-term fix, and I think
disallowing
> HEAD is a reasonable stop-gap measure.
Hi,
I pretty much agree with you that this is the right solution in the long-term.
But how are you going to remember this? Is there an issue tracking? Do you use some other kind of ticketing system?
Since the *official* repo is now hosted on github, why don't making use of the github ticketing system? [1]
You probably already discussed this tons of times but I can't figure out how you are gonna remember to do something if you don't have a roadmap and a ticketing system that allow you to trace the bugs and features.
Do you have to dig into the mailing list archive to look for the previous discussion?
This is actually just out of curiosity, sorry if this hurt someones feeling.
Thanks and regards, Daniele Segato
[1] according to http://git-scm.com/ the link on "Git source repository" is https://github.com/gitster/git