From: Avery Pennarun <apenwarr@gmail.com>
To: Bill Lear <rael@zopyra.com>
Cc: Levente Kovacs <leventelist@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
git@vger.kernel.org
Subject: Re: split up a repository
Date: Wed, 3 Mar 2010 14:19:12 -0500 [thread overview]
Message-ID: <32541b131003031119i5f7baefelc2784ccca90eca41@mail.gmail.com> (raw)
In-Reply-To: <19342.27760.544227.835077@blake.zopyra.com>
On Wed, Mar 3, 2010 at 9:04 AM, Bill Lear <rael@zopyra.com> wrote:
> Does git-subtree support branching of the "main" repository and
> sub-trees in coordinated (one step) fashion?
Yes.
Avery
prev parent reply other threads:[~2010-03-03 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 0:12 split up a repository Kovacs, Levente
2010-03-02 0:36 ` Chris Packham
2010-03-02 10:40 ` Sverre Rabbelier
2010-03-02 23:21 ` Levente Kovacs
2010-03-02 23:19 ` Sverre Rabbelier
2010-03-03 1:40 ` Avery Pennarun
2010-03-03 14:04 ` Bill Lear
2010-03-03 19:19 ` 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=32541b131003031119i5f7baefelc2784ccca90eca41@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=leventelist@gmail.com \
--cc=rael@zopyra.com \
--cc=srabbelier@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).