From: "Paulo J. Matos" <paulo@matos-sorge.com>
To: git@vger.kernel.org
Subject: Re: Special branch for remote
Date: Wed, 27 Jul 2011 15:36:28 +0100 [thread overview]
Message-ID: <j0p7pc$q51$2@dough.gmane.org> (raw)
In-Reply-To: <4E302229.4030402@cisco.com>
On 27/07/11 15:35, Phil Hord wrote:
>
> You can also manage this with submodules [2] or subtree-merge [3].
>
> I prefer submodules since it keeps the huge stuff (docs and bins) away
> from my source code and makes my source code repo much more responsive.
>
Thanks Phil, I will be looking at this solution then.
Cheers,
--
PMatos
prev parent reply other threads:[~2011-07-27 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 8:18 Special branch for remote Paulo J. Matos
2011-07-27 14:35 ` Phil Hord
2011-07-27 14:36 ` Paulo J. Matos [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='j0p7pc$q51$2@dough.gmane.org' \
--to=paulo@matos-sorge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.