savannah-hackers-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers-public] Re: Overwriting bare repositories' master


From: Han-Wen Nienhuys
Subject: [Savannah-hackers-public] Re: Overwriting bare repositories' master
Date: Sun, 05 Nov 2006 13:59:38 +0100
User-agent: Thunderbird 1.5.0.7 (X11/20061027)

Sylvain Beucler escreveu:
Ok, current I created http://git.sv.gnu.org/r/lilypond.git/ . It will
start appearing at http://git.sv.gnu.org/gitweb/ when non-empty.
THat's great. We'll start to play with this soon. In the meantime, could you also create an mftrace GIT repository? It should probably be a separate project on savannah too.

If it's officially part of GNU Lilypond, maybe it's better to keep it
as part of it - I let you see.

It's not part of GNU LilyPond, it was just the most convenient place to put the CVS repository at the time.

GIT repositories can contain multiple branches, and GIT encourages to use them, although some people seem to find it confusing (when compared to other systems)
Ok. What I wonder is why you'd rather have separate sub-repositories
then :)
It's more practical to work with, but as Linus remarked it's not really an issue, and probably easier for a distribution point (like savannah) as you can change things as you go.

I didn't get it :/ Which one is easier?

A single repository is easier for distribution: only one repo to manage access rights, backup etc. for. When developing with GIT, one usually keeps one branch of the repo checked out. This means that when developing, you'd typically have one repo per subproject.

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]