2007/2/27, John Mandereau <[EMAIL PROTECTED]>:
depending whether all stuff on the translation branch is ready to be
released.
May the translation branches be named topic/master-translation and
topic/stable-2.10-translation? or rather translation/master and
translation/stable-2.10?
Maybe lilypo
Hi,
On Mon, 5 Mar 2007, Graham Percival wrote:
> cd /path/to/main/source/tree
> git checkout web/master
> git clone -l -s -n . web
> git checkout master (or whatever branch you normally track)
A good recipe!
> # make sure that web/.git/config contains lines that look something like this:
> [r
Mats Bengtsson wrote:
I know very little about GIT, but if I understand you correctly, the
main reason
to do the clone locally is to save disk space and bandwidth, right?
Yes. Since git keeps all changes for the entire repo, there's no point
in storing all that data twice. If we used a sepa
Brett Duncan wrote:
I'm sure you recall helping me to try and resolve the problem I was
having with chord names and the Verdana font. I wanted to let you know
where that ended up, mainly because there might be an issue that the
developers of Lilypond may need to be aware of.
Actually, I don't
Hi,
On Mon, 5 Mar 2007, Mats Bengtsson wrote:
> I know very little about GIT, but if I understand you correctly, the
> main reason to do the clone locally is to save disk space and bandwidth,
> right?
Right.
> Otherwise it seems to me that it would be simpler to just make two
> separate clon
I know very little about GIT, but if I understand you correctly, the
main reason
to do the clone locally is to save disk space and bandwidth, right?
Otherwise
it seems to me that it would be simpler to just make two separate clones
of the
remote repository, assuming that you have a good internet
