Le 31/01/2012 14:21, David Kastrup disait :
David Kastrupd...@gnu.org writes:
Graham Percivalgra...@percival-music.ca writes:
The updated CG instructions for setting up git manually specify to
use clone:
http://lilypond.org/doc/v2.15/Documentation/contributor/setting-up
but the latest
On Sat, Feb 04, 2012 at 02:14:56PM +0100, Jean-Charles Malahieude wrote:
* git clone learned --single-branch option to limit cloning to a
single branch (surprise!).
This might change things end be quite useful!
Thanks for the news, but in this case it's actually the opposite:
we _want_
, which I'm sure that I don't,
wouldn't this make getting other branches (notably origin/staging,
but also dev/whatever as well) much harder?
Is there a compelling reason not to use git clone for lily-git.tcl
as well?
- Graham
___
lilypond-devel mailing
get specific branches?
IIRC, that is the default of git clone.
If I understand git correctly, which I'm sure that I don't,
wouldn't this make getting other branches (notably origin/staging,
but also dev/whatever as well) much harder?
Is there a compelling reason not to use git clone for lily
David Kastrup d...@gnu.org writes:
Graham Percival gra...@percival-music.ca writes:
The updated CG instructions for setting up git manually specify to
use clone:
http://lilypond.org/doc/v2.15/Documentation/contributor/setting-up
but the latest patch for lily-git.tcl still appears to use the
