On 3/27/09 7:24 AM, "Jan Nieuwenhuizen" <janneke-l...@xs4all.nl> wrote:
> Op donderdag 26-03-2009 om 21:06 uur [tijdzone +0800], schreef Graham
> Percival:
>
>>> GIT from git.sv.gnu.org
>>> git clone git://git.sv.gnu.org/lilypond.git
>>
>> This does not set up easy pulling or pushing in the future, and
>> generally assumes that people know how to use git
>
>>> To get the main source code and documentation,
>>> mkdir lilypond; cd lilypond
>>> git init-db
>>> git remote add -f -t master -m master origin
>>> git://git.sv.gnu.org/lilypond.git/
>>> git checkout -b master origin/master
>>
>> After approximately four hours of discussion between git experts
>> and non-experts, we decided that this is the best sequence of
>> commands for most contributors.
>
> Well, this is utterly ridiculous IMNSHO. I would suggest to
>
> * fix the main lilypond repo so that git clone "just works", or
> * ask on g...@vger.kernel.org what else we're doing wrong, or
> * fix git so that git clone "just works"
>
> If all of these fail, and git clone is *supposed* to be utterly
> unusable, I suggest to look seriously into switching to bazaar or hg.
Please, let's not change the version control system again. Git works well
once you get on it.
We're talking about a one-time difference of three commands vs. one command.
If it "just worked", we'd have one command:
git clone git://git.sv.gnu.org/lilypond.git
If it doesn't, we have a *one-time* use of three commands:
git init-db
git remote add -f -t master -m master origin
git://git.sv.gnu.org/lilypond.git/
(note -- the git remote command is word-wrapped onto two lines).
git checkout -b master origin/master
Once this is done, it's good to go.
I'm not opposed to making it *just work*. I am opposed to switching from
git just because of this minor inconvenience.
Carl
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
