From: Peter Karlsson <peter@softwolves.pp.se>
To: Git Mailing List <git@vger.kernel.org>
Subject: Canonical method of merging two projects
Date: Mon, 14 Apr 2008 07:37:17 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0804140733500.7014@ds9.cixit.se> (raw)
Hi!
What is the canonical way of merging an unrelated project into another
so that all of the merged project's files appear in a sub-directory of
the first?
I have two projects, A with files "a.txt" and "b.txt", and B with files
"a.txt" and "c.txt", each in a separate Git repoistory. I want to merge
those two projects, throwing away the B repository, and achieve a
file layout that has "a.txt" and "b.txt" from A, and "B/a.txt" and
"B/c.txt" from B. I.e, the two files with the same name are unrelated,
and all of B's file should end up in a sub-directory.
I do not want to use submodules, since I am planning on throwing B
away.
When I did this, I did a regular "git merge --no-commit", and then
moved the files manually. Thankfully, I only had one duplicated file
name, so fixing the conflict was easy enough. I looked through the
git-merge manual page, but could not find any information about this
use-case.
--
\\// Peter - http://www.softwolves.pp.se/
next reply other threads:[~2008-04-14 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 6:37 Peter Karlsson [this message]
2008-04-14 6:56 ` Canonical method of merging two projects Gabriel
2008-04-14 18:10 ` Eric Raible
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=Pine.LNX.4.64.0804140733500.7014@ds9.cixit.se \
--to=peter@softwolves.pp.se \
--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).