From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Do not ignore hidden refs
Date: Sat, 18 Nov 2006 20:55:20 +0100 [thread overview]
Message-ID: <20061118195520.GQ7201@pasky.or.cz> (raw)
In-Reply-To: <7vejs0cz5s.fsf@assigned-by-dhcp.cox.net>
On Sat, Nov 18, 2006 at 08:50:23PM CET, Junio C Hamano wrote:
> Petr Baudis <pasky@suse.cz> writes:
>
> > On Sat, Nov 18, 2006 at 08:27:09AM CET, Junio C Hamano wrote:
> >> ... I do not think it is a great
> >> enough convention to be promoted as the official BCP, but it has
> >> been good enough for me, ...
> >
> > That's way too arbitrary for my taste, I think I needn't explain why.
>
> Because _I_ explained why already ;-).
Oops. ;-) Me too sloppy today, sorry.
> > What about leading underscore?
>
> I would rather prefer to do refs/{heads,private}/ and allow
> checkout to treat either of them as branches. We are talking
> about allowing checkout to go to a non-branch by storing a raw
> commit object name in HEAD instead of leaving it as a symref, so
> we know we are going to touch that area already.
Cogito _heavily_ assumes on a lot of places that heads live in
refs/heads/ and tags live in refs/tags/. Besides, I think private tags
are much more useful to support than private heads (not that you would
necessarily make more private tags than private heads, but you are more
likely to want tags autopushed than heads; or perhaps that just in my
head?). So what about refs/{heads,tags}/private/? :-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
The meaning of Stonehenge in Traflamadorian, when viewed from above, is:
"Replacement part being rushed with all possible speed."
next prev parent reply other threads:[~2006-11-18 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 4:11 [PATCH] Do not ignore hidden refs Petr Baudis
2006-11-18 4:39 ` Junio C Hamano
2006-11-18 4:53 ` Petr Baudis
2006-11-18 7:27 ` Junio C Hamano
2006-11-18 7:41 ` Shawn Pearce
2006-11-18 19:28 ` Petr Baudis
2006-11-18 19:50 ` Junio C Hamano
2006-11-18 19:55 ` Petr Baudis [this message]
2006-11-18 20:05 ` Junio C Hamano
2006-11-18 23:18 ` Petr Baudis
2006-11-19 0:29 ` Junio C Hamano
2006-11-19 0:48 ` Petr Baudis
2006-11-18 17:35 ` Linus Torvalds
2006-11-18 18:35 ` Junio C Hamano
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=20061118195520.GQ7201@pasky.or.cz \
--to=pasky@suse.cz \
--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