Re: Cloning into an existing, non-empty directory?
- From
Richard Hartmann <richih.mailinglist@gmail.com>
- Date
- Apr 23, 2011, 22:11 UTC
- Message-ID
- <BANLkTinV4cFC5vzr25V-D3PMwWx284zgoQ@mail.gmail.com>
- In-Reply-To
- <20110423101500.GB1500@elie>
2011/4/23 Jonathan Nieder <jrnieder@gmail.com>:
> Richard Hartmann wrote[1]:
Nice. Is that automagic? And if yes, may I steal it?
> I assume you mean --work-tree and --git-dir. But if true, that would > be a bug.
With env variables set:
% git merge origin fatal: origin - not something we can merge %
With parameters:
% git '--work-tree=/home/richih/killme/fgit/target-default' '--git-dir=/home/richih/killme/fgit/source' merge origin fatal: origin - not something we can merge %
In a normal worktree without any mangling: % git merge origin [...success...] %
I think I reduced the test-case as much as I can, especially since the script takes care of everything for you. If you simply run in on any random git repo, you will be able to replicate this behaviour. Unfortunately ;)
Thanks, Richard