From: Alex Riesen <raa.lkml@gmail.com>
To: Wink Saville <wink@saville.com>
Cc: git@vger.kernel.org
Subject: Re: How-to combine several separate git repos?
Date: Mon, 10 Dec 2007 08:52:31 +0100 [thread overview]
Message-ID: <20071210075231.GA2984@steel.home> (raw)
In-Reply-To: <475C3E25.30704@saville.com>
Wink Saville, Sun, Dec 09, 2007 20:12:37 +0100:
>> You can merge them, for example:
>>
>> $ cd project1
>> $ git merge project2/master
>>
> Starting over (restoring the original from a tar backup)
> this didn't work I get:
>
> wink@ic2d1:$ cd StateMachine
> wink@ic2d1:$ git merge ../test2/master
> ../test2/master - not something we can merge
This is *not* what I suggested. It should be:
$ git config ... (as suggested before)
$ git fetch test2
$ git merge test2/master
Here test2/master - is *NOT* a path. It is the name of the branch
where the local repository stores reference to the commit
corresponding to the master of remote repo (that is: the "master"
branch of "test2", as seen from the repository where you do the
merge).
> So the first suggestion works, but I don't want them as
> separate branches as I want to work on the simultaneously
> and they'll share common code.
Sound like the secode (merge) approach
> Another option I was thinking would work for me would be to use
> submodules. But I'm not sure submodules are ready for
> neophytes and maybe it doesn't do what I want?
They are ready for some (dunno if they'd like to be called neophytes).
I just don't think you need them (keywords on your explanations being
"share common code", understanding them as "the modules use the common
code simultaneously").
next prev parent reply other threads:[~2007-12-10 7:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 6:34 How-to combine several separate git repos? Wink Saville
2007-12-09 10:43 ` Alex Riesen
2007-12-09 19:12 ` Wink Saville
2007-12-09 19:55 ` Daniel Barkalow
2007-12-09 23:44 ` Wink Saville
2007-12-10 1:11 ` Daniel Barkalow
2007-12-10 2:29 ` Wink Saville
2007-12-10 3:01 ` Daniel Barkalow
2007-12-10 6:36 ` Wink Saville
2007-12-10 6:51 ` Daniel Barkalow
2007-12-10 7:01 ` Wink Saville
2007-12-10 7:52 ` Alex Riesen [this message]
2007-12-10 17:55 ` Wink Saville
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=20071210075231.GA2984@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=wink@saville.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).