git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emily Ren <lingyan.ren@gmail.com>
To: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Cc: git@vger.kernel.org
Subject: Re: how to merge sub directory or file?
Date: Tue, 8 Nov 2011 15:08:00 +0800	[thread overview]
Message-ID: <CAP_m3yKehN1-KtMCVxKdu2ca59GzYE0w2X2=UhH2X9PgzYiMAg@mail.gmail.com> (raw)
In-Reply-To: <20111107193708.6cf2ae81.kostix@domain007.com>

Hi Kon,

Thank you !  I tried that method, it failed on read-tree because
B/dir3 already exists, Cannot bind.

$ git read-tree --prefix=dir3 -u A:dir3
error: Entry 'dir3/file1' overlaps with 'dir3/file1'.  Cannot bind.

And my case is that not all A's sub direcotries are in B.
For example, in A's dir3, there are file1, dir4 and dir5. But in B's
dir3, only file1 and dir4 exist, there's no dir5. How to handle this
case ?

Thanks,
Emily

On Mon, Nov 7, 2011 at 11:37 PM, Konstantin Khomoutov
<flatworm@users.sourceforge.net> wrote:
>
> On Mon, 7 Nov 2011 22:54:18 +0800
> Emily <lingyan.ren@gmail.com> wrote:
>
> > I have two git projects A and B, content of B is subset of A. For
> > example, Project  A and B's tree are as below:
> [...]
> > When there's new changes in project A, how can I merge them to
> > project B without changing B's directory structure?
> >
> > Your help will be highly appreciated.
> Subtree merging maybe?
> See http://progit.org/book/ch6-7.html

      reply	other threads:[~2011-11-08  7:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 13:26 BUG. Git config pager when --edit Alexey Shumkin
2011-11-07 13:43 ` Frans Klaver
2011-11-07 16:42   ` Jeff King
2011-11-07 17:02     ` Junio C Hamano
2011-11-07 17:18       ` Jeff King
2011-11-07 20:45         ` Frans Klaver
2011-11-07 14:54 ` how to merge sub directory or file? Emily
2011-11-07 15:37   ` Konstantin Khomoutov
2011-11-08  7:08     ` Emily Ren [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='CAP_m3yKehN1-KtMCVxKdu2ca59GzYE0w2X2=UhH2X9PgzYiMAg@mail.gmail.com' \
    --to=lingyan.ren@gmail.com \
    --cc=flatworm@users.sourceforge.net \
    --cc=git@vger.kernel.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 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).