Hi, On Tue, 17 Feb 2009, Graham Percival wrote:
> On Mon, Feb 16, 2009 at 06:36:24PM -0700, Andrew Hawryluk wrote: > > In the instructions for getting the source code, why not just use > > git-clone? Is there a difference? The currently suggested method of > > remote-add + checkout produces a bunch of warnings (below). Sorry, missed the original mail. These warnings should not be an issue with an up-to-date Git (1.6.1.3 is the latest incarnation). > 1. git-clone gets the entire repo, not just the particular > branch that you want. Indeed, but as Git is pretty efficient, simplicity beats correctness here. > 2. We don't want newbies switching between branches, because > (speaking from experience) that wastes 1-5 hours of frustrating > time-wasting when you're just trying to work on lilypond. I agree. Before you understand the ways branches can split at a common commit and come together again at a merge commit (and all kinds of weird criss-cross merge scenarios), this is more than just confusing. > 3. I'm not certain if git-clone setups up everything for doing > "git pull origin" and "git push origin". Yes, it does (as long as you work on the 'master' branch, or whatever is marked in the upstream repository as current). Ciao, Dscho _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
