From: Tomas Carnecky <tom@dbservice.com>
To: Patrick Doyle <wpdster@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git remote vs. submodules
Date: Thu, 11 Nov 2010 16:00:07 +0100 [thread overview]
Message-ID: <4CDC04F7.6080801@dbservice.com> (raw)
In-Reply-To: <AANLkTin=t7RoLTwxc1KOv7_vZi-OgD_Jcu+66-fte6Sq@mail.gmail.com>
On 11/11/10 3:44 PM, Patrick Doyle wrote:
> On Thu, Nov 11, 2010 at 6:34 AM, Tomas Carnecky <tom@dbservice.com> wrote:
>> Are you maybe looking for a subtree merge?
>> http://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html
>
> Yeah, that looks like it. I never would have hit upon the read-tree
> step by myself -- I would have just laid things out with the prefix
> already embedded in the subprojects.
>
> Hmmm... it seems to me that feeding changes back to the subprojects
> might be difficult (and that is born out by a comment at the end of
> the page you referenced.)
https://github.com/apenwarr/git-subtree, it makes exactly that easier.
tom
next prev parent reply other threads:[~2010-11-11 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 1:45 git remote vs. submodules Patrick Doyle
2010-11-11 11:34 ` Tomas Carnecky
2010-11-11 14:44 ` Patrick Doyle
2010-11-11 15:00 ` Tomas Carnecky [this message]
2010-11-11 15:11 ` Patrick Doyle
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=4CDC04F7.6080801@dbservice.com \
--to=tom@dbservice.com \
--cc=git@vger.kernel.org \
--cc=wpdster@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).