From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Paul Drews <paul.drews@intel.com>,
git@vger.kernel.org, Lars Hjemli <hjemli@gmail.com>
Subject: Re: rebase not honoring core.worktree pointing elsewhere
Date: Thu, 4 Nov 2010 21:20:05 +0700 [thread overview]
Message-ID: <AANLkTi=DJMLdHD2t2znS4eA57LnTfcPhLUaPbJktE7NB@mail.gmail.com> (raw)
In-Reply-To: <20101103161311.GA12934@burratino>
On Wed, Nov 3, 2010 at 11:13 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Paul Drews wrote:
>> Nguyen Thai Ngoc Duy <pclouds <at> gmail.com> writes:
>
>>> Another one: create a .git file with this line and put it in worktree's
>>> topdir
>>>
>>> gitdir: /path/to/real/git.dir
>>>
>>> See gitrepository-layout.txt.
>>
>> Ooh! That would be my favorite, since it's a documented legal usage.
>
> By the way, .git symlinks have been historically supported and are not
> likely to break, either. Maybe gitrepository-layout should grow to
> include a section on the repository search.
>
>> Unfortunately, although the rebase scenario works that way a local
>> "git clone" doesn't work:
>>
>> # git clone /abs/path/to/proj
>> Cloning into proj...
>> fatal: failed to open '/abs/path/to/proj/objects': No such file or directory
>
> enter_repo() never learned .git file support, though I see no reason it should
> be hard to add.
Also get_repo_path(). By the way if you work on this, please move
enter_repo() to setup.c. Keeping it close to setup_* functions may
increase the chance that it also gets fixed along with setup_*.
Another thing. "git init" should probably learn to create .git file.
Each time I use .git file I have to look at man page^W^Wsource code
again to know its syntax.
--
Duy
prev parent reply other threads:[~2010-11-04 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 17:22 rebase not honoring core.worktree pointing elsewhere Paul Drews
2010-11-01 17:38 ` Sverre Rabbelier
2010-11-02 0:11 ` Nguyen Thai Ngoc Duy
2010-11-02 1:21 ` Junio C Hamano
2010-11-02 16:26 ` Paul Drews
2010-11-03 0:13 ` Nguyen Thai Ngoc Duy
2010-11-03 15:41 ` Paul Drews
2010-11-03 15:52 ` Nguyen Thai Ngoc Duy
2010-11-03 16:13 ` Jonathan Nieder
2010-11-04 14:20 ` Nguyen Thai Ngoc Duy [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='AANLkTi=DJMLdHD2t2znS4eA57LnTfcPhLUaPbJktE7NB@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=jrnieder@gmail.com \
--cc=paul.drews@intel.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).