From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [PATCH] Do not ignore hidden refs
Date: Sat, 18 Nov 2006 10:35:47 -0800 [thread overview]
Message-ID: <7vr6w0eh6k.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0611180933360.3692@woody.osdl.org> (Linus Torvalds's message of "Sat, 18 Nov 2006 09:35:18 -0800 (PST)")
Linus Torvalds <torvalds@osdl.org> writes:
> On Sat, 18 Nov 2006, Petr Baudis wrote:
>>
>> Some of the ref manipulation tools (git-for-each-ref and git-show-ref in
>> particular) would not handle hidden (~ /^\./) refs. This may be an
>> acceptable or possibly even desirable behaviour for the ref walkers and
>> repackers, but git-show-ref hiddenrefname must work.
>
> No.
>
> Refnames MUST NOT start with a ".".
>
> It's not even about the traditional unix "hidden file" thing. It's simply
> a syntactic issue. A ref cannot start with a ".", because we use things
> like ".." and "..." to separate them.
We do not forbid a refname that ends with a ".", but I think it
was a mistake. We _can_ disambiguate the ones that begin with a
"." by saying "whatever..heads/.I-begin-with-dot", but not the
ones that end with "heads/I-end-with-dot...end-of-range".
prev parent reply other threads:[~2006-11-18 18:35 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
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 [this message]
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=7vr6w0eh6k.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=torvalds@osdl.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