From: Junio C Hamano <junkio@cox.net>
To: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: git@vger.kernel.org
Subject: Re: multiple branches or multiple repositories
Date: Thu, 02 Nov 2006 18:38:01 -0800 [thread overview]
Message-ID: <7vlkmtmf06.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <eie7ae$ib6$1@sea.gmane.org> (Han-Wen Nienhuys's message of "Fri, 03 Nov 2006 02:51:30 +0100")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> We're in the process of converting the LilyPond CVS repository at
> savannah.gnu.org to GIT. One of the questions we need to deal with,
> is how handle modules.
>
> There seem to be two approaches:
>
> - 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?
As the layout for a distribution point, the second one may be
easier to handle (one place to remotely sync with), but in all
other aspects the first option should be easier to deal with
day-to-day.
next prev parent reply other threads:[~2006-11-03 2:38 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 [this message]
2006-11-03 7:11 ` Linus Torvalds
2006-11-03 16:01 ` Jeff King
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=7vlkmtmf06.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.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 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.