From: Julian Phillips <julian@quantumfyre.co.uk>
To: Peter Baumann <waste.manager@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [BUG] git-new-workdir doesn't understand packed refs
Date: Wed, 18 Apr 2007 12:55:15 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0704181251040.19261@reaper.quantumfyre.co.uk> (raw)
In-Reply-To: <20070418081122.GB32634@xp.machine.xx>
On Wed, 18 Apr 2007, Peter Baumann wrote:
> On Wed, Apr 18, 2007 at 12:40:10AM -0700, Junio C Hamano wrote:
>>
>> We can do one of two things. I am not sure which one is better.
>>
>> (0) The effect of 'git gc' by definition in the symlink-shared
>> work tree should be the same as in the original repository
>> as the former is to share all the refspace and object
>> database. So we _could_ declare that running 'git gc' in
>> symlink-shared work tree is insane and educate people to
>> run that in the original repository. This is _not_ doing
>> anything.
>>
>> (1) We could by convention declare a worktree whose .git/refs
>> is a symlink, and have git-gc and friends check for it, and
>> either refuse to run or automatically chdir and run there.
>>
>> If we were to do this, we probably should check more than
>> just .git/refs but some other symlinks under .git/ as well.
>>
>> (2) We could dereference .git/packed-refs, when it is a
>> symlink, by hand, just like we dereference a symlink HEAD
>> by hand (see resolve_ref() in refs.c), and run the
>> creat-to-temp-and-then-rename sequence to update the real
>> file that is pointed at by it.
>>
>
> Its not all the clear which one is the best, but (2) sounds as the most
> promosing aproach. Hopefully, I'll have time to cook up a patch this
> evening.
Personally I think (1) might be slightly better, in the refuse to run
form. gc is a repository operation, not a working directory one - and by
refusing to run in a workdir this is made clear. You could print out a
message that includes the location of the actual repo to be more friendly
though.
But whatever solution you go for, you can't use _any_ workdir that points
at a repo that is having gc run on, either directly or indirectly, without
risky odd behaviour.
--
Julian
---
Q: How many supply-siders does it take to change a light bulb?
A: None. The darkness will cause the light bulb to change by itself.
next prev parent reply other threads:[~2007-04-18 11:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 16:17 [BUG] git-new-workdir doesn't understand packed refs Peter Baumann
2007-04-17 21:55 ` Julian Phillips
2007-04-18 5:52 ` Peter Baumann
2007-04-18 7:26 ` Julian Phillips
2007-04-18 7:40 ` Junio C Hamano
2007-04-18 8:11 ` Peter Baumann
2007-04-18 11:55 ` Julian Phillips [this message]
2007-04-18 16:23 ` Junio C Hamano
2007-04-18 17:43 ` Peter Baumann
2007-04-18 18:17 ` Junio C Hamano
2007-04-18 18:31 ` Peter Baumann
2007-04-18 18:42 ` Junio C Hamano
2007-04-18 21:08 ` Peter Baumann
2007-04-18 21:31 ` Junio C Hamano
2007-04-19 5:35 ` [PATCH] Add test for symlinked .git/packed-refs Peter Baumann
2007-04-19 6:06 ` Junio C Hamano
2007-04-20 16:52 ` [PATCH] pack-refs: dereference .git/packed-refs if it is a symlink Peter Baumann
2007-04-21 20:05 ` Junio C Hamano
2007-04-18 18:43 ` [BUG] git-new-workdir doesn't understand packed refs Julian Phillips
2007-04-18 10:28 ` [PATCH] pack-refs: dereference .git/packed-refs if it is a symlink Peter Baumann
2007-04-18 16:09 ` Linus Torvalds
2007-04-18 17:47 ` Peter Baumann
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0704181251040.19261@reaper.quantumfyre.co.uk \
--to=julian@quantumfyre.co.uk \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=waste.manager@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).