[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 854 in lilypond: lilycontrib.tcl
From: |
codesite-noreply |
Subject: |
Issue 854 in lilypond: lilycontrib.tcl |
Date: |
Mon, 05 Oct 2009 01:33:07 +0000 |
Comment #1 on issue 854 by Carl.D.Sorensen: lilycontrib.tcl
http://code.google.com/p/lilypond/issues/detail?id=854
I've looked at this, and I think I've added the minimum functionality to
make it work.
It will initialize a repository (from savannah, instead of repo).
It will automatically create a patch from origin/master.
As long as it works well, it should be convenient. But I'm concerned that
if it gets an error, it will be a support
nightmare.
There is no commit functionality. I don't think it makes sense to create
commit functionality; it would just be
a duplicate of git gui. And if they use git gui, they'll gradually get
more up to speed on git, which I think is a
good thing.
I'd like to invite some frogs to try it out, to see how it looks.
On my system, I can't make it run by typing lilycontrib.tcl. Instead, I
have to type
wish lilycontrib.tcl.
As far as testing is concerned, you will probably want to change the line
set lily_dir $env(HOME)/lilypond
to
set lily_dir $env(HOME)/lilypond-test
so that you won't overwrite your current lilypond repository, if you have
one.
Thanks,
Carl
Attachments:
lilycontrib.tcl 3.5 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings