git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Git List" <git@vger.kernel.org>, "Nguyễn Thái Ngọc" <pclouds@gmail.com>
Subject: Re: Cloning into an existing, non-empty directory?
Date: Sun, 24 Apr 2011 00:11:11 +0200	[thread overview]
Message-ID: <BANLkTinV4cFC5vzr25V-D3PMwWx284zgoQ@mail.gmail.com> (raw)
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

  parent reply	other threads:[~2011-04-23 22:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 21:27 Cloning into an existing, non-empty directory? Richard Hartmann
2011-04-21 22:03 ` Jonathan Nieder
2011-04-22 11:21   ` Richard Hartmann
2011-04-23 10:15     ` Jonathan Nieder
2011-04-23 10:28       ` Nguyen Thai Ngoc Duy
2011-04-23 10:37         ` Jonathan Nieder
2011-04-23 22:11       ` Richard Hartmann [this message]
2011-04-25  8:00         ` Jonathan Nieder
2011-04-25  8:40           ` Andreas Schwab
2011-04-25  8:59             ` Jonathan Nieder
2011-04-25 18:37               ` Jeff King
2011-04-25 14:08           ` Richard Hartmann

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=BANLkTinV4cFC5vzr25V-D3PMwWx284zgoQ@mail.gmail.com \
    --to=richih.mailinglist@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=pclouds@gmail.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).