From: Andreas Ericsson <ae@op5.se>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Eric Wong <normalperson@yhbt.net>,
Martin Langhoff <martin.langhoff@gmail.com>,
git@vger.kernel.org
Subject: Re: git-svn and huge data and modifying the git-svn-HEAD branch directly
Date: Wed, 01 Mar 2006 17:07:26 +0100 [thread overview]
Message-ID: <4405C6BE.2000706@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0603010745320.22647@g5.osdl.org>
Linus Torvalds wrote:
>
> On Wed, 1 Mar 2006, Andreas Ericsson wrote:
>
>>Eric Wong wrote:
>>
>>>Should rev-parse be taught to be less strict and look for basenames
>>>that can't be found in heads/ and tags/ in other directories?
>>
>>It already does. The search order is this, for a ref named 'foo':
>> $GIT_DIR/foo
>> $GIT_DIR/refs/foo
>> $GIT_DIR/refs/tags/foo
>> $GIT_DIR/refs/heads/foo
>
>
> Yes, but I think Eric wanted to avoid having to write the prefix part,
> which git won't let you do right now.
>
> If you have a ref in .git/refs/svn-tracker/git-svn-HEAD, you would have to
> write out all of "svn-tracker/git-svn-HEAD", because unlike a "real
> branch", get_sha1() won't look into the "svn-tracker" without it being
> explicitly mentioned.
>
> Now, some tools will actually do "for_each_ref()" and check the ref-name
> against each of them (so if you pass in "foo", it will check them afainst
> _any_ ref-subdirectory that contains "foo"). But get_sha1() won't.
>
Didn't know that. The day is not a complete waste then.
> We could fix get_sha1(), but part of the logic was that other
> subdirectories are special, and as such they _should_ be mentioned, so
> that a file in such a special directory isn't ever confused with a real
> branch.
>
> But if you were to use for example .git/refs/git-svn/tracking as the
> svn-tracking reference head, and then you'd be perfectly able to use
>
> git log git-svn/tracking..
>
> to see what you've done since the last svn import?
>
Personally I'm all for namespace separation. I'm assuming the script has
the tracker-branch hardcoded anyway, so I don't really understand why it
would be necessary to keep other refs in a separate directory and, if it
*is* necessary, why that subdirectory can't be .git/refs/heads/svn.
Eric mentioned earlier that the tracking-branch can't be committed to
(ever), so the user convenience for searching other directories should
be nearly non-existant.
Perhaps I'm missing something obvious. Perhaps I'm just stupid. Perhaps
the pub just opened and I don't feel like reading it twice to make sure
I understood. ;)
--
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-03-01 16:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 17:59 git-svn and huge data and modifying the git-svn-HEAD branch directly Nicolas Vilz 'niv'
2006-02-27 18:46 ` Eric Wong
2006-02-27 18:55 ` Jan Harkes
2006-02-27 19:24 ` Eric Wong
2006-02-28 0:25 ` Martin Langhoff
2006-02-28 0:41 ` Linus Torvalds
2006-02-28 0:58 ` Martin Langhoff
2006-03-01 6:51 ` Eric Wong
2006-03-01 9:40 ` Andreas Ericsson
2006-03-01 15:53 ` Linus Torvalds
2006-03-01 16:07 ` Andreas Ericsson [this message]
2006-03-01 16:24 ` Linus Torvalds
2006-03-01 17:14 ` Josef Weidendorfer
2006-03-01 17:28 ` Shawn Pearce
2006-03-01 17:40 ` Linus Torvalds
2006-03-01 18:06 ` Josef Weidendorfer
2006-03-01 18:25 ` Linus Torvalds
2006-03-01 20:26 ` Josef Weidendorfer
2006-03-01 21:28 ` Linus Torvalds
2006-03-01 19:11 ` Junio C Hamano
2006-03-01 20:54 ` Josef Weidendorfer
2006-03-01 21:40 ` Martin Langhoff
2006-03-01 23:23 ` Carl Worth
2006-03-01 23:43 ` Linus Torvalds
2006-03-01 21:07 ` Johannes Schindelin
2006-03-19 19:12 ` Petr Baudis
2006-03-19 19:35 ` Linus Torvalds
2006-03-19 19:43 ` Junio C Hamano
2006-02-27 19:04 ` [PATCH] contrib/git-svn: tell the user to not modify git-svn-HEAD directly Eric Wong
2006-02-27 19:34 ` git-svn and huge data and modifying the git-svn-HEAD branch directly Nicolas Vilz 'niv'
2006-02-27 20:27 ` Eric Wong
2006-02-27 20:47 ` Nicolas Vilz 'niv'
2006-02-27 20:55 ` [PATCH] contrib/git-svn: correct commit example in manpage Eric Wong
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=4405C6BE.2000706@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=normalperson@yhbt.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.