From: Wink Saville <wink@saville.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: How-to combine several separate git repos?
Date: Sun, 09 Dec 2007 18:29:10 -0800 [thread overview]
Message-ID: <475CA476.6070507@saville.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712091942520.5349@iabervon.org>
Daniel Barkalow wrote:
> On Sun, 9 Dec 2007, Wink Saville wrote:
>
> <snip>
>
I got submodule working, buy following the tutorial here:
http://git.or.cz/gitwiki/GitSubmoduleTutorial#preview.
As well as looking at:
http://jonathan.tron.name/articles/2007/09/15/git-1-5-3-submodule
http://en.wikibooks.org/wiki/Source_Control_Management_With_Git/Submodules_and_Superprojects#endnote_lie_parent
http://kerneltrap.org/mailarchive/git/2007/10/19/348810
http://kerneltrap.org/mailarchive/git/2007/10/19/348829
I'd say the current documentation in git needs to improve at least
for neophytes. The first step would be to include the GitSubmoduleTutorial.
Also, I think the second paragraph of the tutorial is very important and
something like it should probably be the first paragraph of the
git-submodule
man page:
"Submodules maintain their own identity; the submodule support just
stores the submodule repository location and commit ID, so other
developers who clone the superproject can easily clone all the
submodules at the same revision."
My interpretation of the paragraph and how submodules might be used
is that the "supermodule" provides tags for a set of repositories.
I see that as important, especially for large projects which could use
multiple repositories for sub-projects and then use a "supermodule"
for test and release management.
That isn't what I really wanted to do. As a one man band I was looking
to actually "combine" several repositories into one logical repository
to simplify commits, pushes, pulls to my own backup repositories.
I now see that that wasn't the purpose of submodule.
Anyway, that is the perspective of this neophyte and I learned something
new which is a primary goal of mine.
Finally, I'm back to my original question how to combine repositories? As
I said in my response to Alex, the multiple branches I got working but that
isn't what I want.
What I think I now want is to create a new repository which contains my
other repositories as sub-directories (with their histories) after combining
them I would delete the old repositories. I expect the resulting history
to be sequential, with the sequence defined by the order I combine them,
but maybe there is another choice?
Cheers,
Wink Saville
next prev parent reply other threads:[~2007-12-10 2:29 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 [this message]
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
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=475CA476.6070507@saville.com \
--to=wink@saville.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=raa.lkml@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).