git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Subject: multiple branches or  multiple repositories
Date: Fri, 03 Nov 2006 02:51:30 +0100	[thread overview]
Message-ID: <eie7ae$ib6$1@sea.gmane.org> (raw)


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?

-- 
  Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

             reply	other threads:[~2006-11-03  2:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03  1:51 Han-Wen Nienhuys [this message]
2006-11-03  2:38 ` multiple branches or multiple repositories Junio C Hamano
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='eie7ae$ib6$1@sea.gmane.org' \
    --to=hanwen@xs4all.nl \
    --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).