From: Jeff King <peff@peff.net>
To: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: git@vger.kernel.org
Subject: Re: multiple branches or multiple repositories
Date: Fri, 3 Nov 2006 11:01:16 -0500 [thread overview]
Message-ID: <20061103160115.GA27895@coredump.intra.peff.net> (raw)
In-Reply-To: <eie7ae$ib6$1@sea.gmane.org>
On Fri, Nov 03, 2006 at 02:51:30AM +0100, Han-Wen Nienhuys wrote:
> - for each module, create a separate git repository. Inside the
> repository, each subproject has its own branching
>
> - put each module as a separate branch in a shared repository.
>
> I think the first option is the most natural one, but are there any
> issues, besides namespace pollution to the second option?
I don't believe there is currently an option to git-clone to grab only a
single branch, so cloners in the second case would end up having to get
_all_ modules (though such an option would probably not be hard to
implement).
The plus side is that a single 'fetch' would grab updates for all
modules (with only a single connection to the server).
prev parent reply other threads:[~2006-11-03 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 1:51 multiple branches or multiple repositories Han-Wen Nienhuys
2006-11-03 2:38 ` Junio C Hamano
2006-11-03 7:11 ` Linus Torvalds
2006-11-03 16:01 ` Jeff King [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=20061103160115.GA27895@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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).