From: Andreas Ericsson <ae@op5.se>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux@horizon.com, cworth@cworth.org, git@vger.kernel.org
Subject: Re: [PATCH] New git-seek command with documentation and test.
Date: Fri, 24 Feb 2006 11:11:48 +0100 [thread overview]
Message-ID: <43FEDBE4.8040200@op5.se> (raw)
In-Reply-To: <43FEAD62.6050302@zytor.com>
H. Peter Anvin wrote:
> linux@horizon.com wrote:
>
>> The annoying thing about temporary branch names like "bisect" and "seek"
>> is that:
>> a) They clutter up the nae space available to the repository user.
>> Users have to know that those are reserved names.
>> b) If a repository is cloned while they're in use, they might get
>> into a "remotes" file, with even more confusing results.
>>
>> This is somewhat heretical, but how about making a truly unnamed
>> branch by
>> having .git/HEAD *not* be a symlink, but rather hold a commit ID
>> directly?
>> It's already well established that files in the .git directory directly
>> are strictly local to this working directory, so it seems a much better
>> home for such temporary state.
>>
>
> It might be easier to just reserve part of the namespace, e.g. ".bisect"
> and ".seek" instead.
>
Ach, no. Not specific names. ^\.-.* would be acceptable, but I sometimes
use '.name' or '-name' to mark a temporary branch. Making .- or some
such reserved would perhaps make sense, but not with specific names.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-02-24 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 0:29 [PATCH] New git-seek command with documentation and test linux
2006-02-24 0:54 ` Johannes Schindelin
2006-02-24 1:23 ` linux
2006-02-24 6:53 ` H. Peter Anvin
2006-02-24 10:11 ` Andreas Ericsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-14 16:28 several quick questions Nicolas Vilz 'niv'
2006-02-14 17:05 ` Linus Torvalds
2006-02-14 18:10 ` Carl Worth
2006-02-14 18:34 ` Linus Torvalds
2006-02-14 20:10 ` Carl Worth
2006-02-14 20:40 ` Linus Torvalds
2006-02-14 21:53 ` Carl Worth
2006-02-14 22:39 ` Junio C Hamano
2006-02-23 20:31 ` [PATCH] New git-seek command with documentation and test Carl Worth
2006-02-24 0:18 ` J. Bruce Fields
2006-02-24 10:00 ` Andreas Ericsson
2006-02-24 11:38 ` Junio C Hamano
2006-02-24 14:23 ` Carl Worth
2006-02-24 21:48 ` Johannes Schindelin
2006-02-24 21:57 ` J. Bruce Fields
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=43FEDBE4.8040200@op5.se \
--to=ae@op5.se \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=linux@horizon.com \
/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).