From: Avery Pennarun <apenwarr@gmail.com>
To: Mahesh Vaidya <forvaidya@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: sub module branches
Date: Mon, 8 Mar 2010 19:47:13 -0500 [thread overview]
Message-ID: <32541b131003081647j2eadb8dfs758611fd4007deea@mail.gmail.com> (raw)
In-Reply-To: <b42431c81003080314j694114b5o433988470f13328a@mail.gmail.com>
On Mon, Mar 8, 2010 at 6:14 AM, Mahesh Vaidya <forvaidya@gmail.com> wrote:
> I have a situation like
>
> project/source.git
> /submod_1
> /submod_2
>
> I need to modify code in all 3 repos viz. source, submod_1 & submod_2.
>
> If I create branch in source, will it propogate to remaining
> submodules ? or in other words can I have "global branch" and "global
> tag"
You could use git-subtree instead: http://github.com/apenwarr/git-subtree
That will allow you to branch all the repos at once. It slightly
increases the effort required to extract the changes and submit them
upstream again, though.
Have fun,
Avery
prev parent reply other threads:[~2010-03-09 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 11:14 sub module branches Mahesh Vaidya
2010-03-08 13:05 ` Peter Krefting
2010-03-09 0:47 ` Avery Pennarun [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=32541b131003081647j2eadb8dfs758611fd4007deea@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=forvaidya@gmail.com \
--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).