Updates:
Status: Verified
Comment #37 on issue 2092 by philehol...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
Added to desktop and verified push button exists. Will try a push later...
_
Updates:
Labels: -fixed_2_15_31 fixed_2_15_30
Comment #36 on issue 2092 by gra...@percival-music.ca: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
(No comment was entered for this change.)
___
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_31
Comment #35 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
Pushed to staging as 0a1bb6351826eb3d0d857d5dedf707f8ba58d920
Val
Updates:
Labels: -Patch-countdown Patch-push
Comment #34 on issue 2092 by colinpkc...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
Counted down to 20120214, please push.
__
Updates:
Labels: Patch-review
Comment #32 on issue 2092 by d...@gnu.org: lily-git.tcl should using
a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c32
Patchy the autobot says: LGTM. But adds an empty line at EOF.
__
Updates:
Labels: Patch-new
Comment #31 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c31
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If
Comment #30 on issue 2092 by gra...@percival-music.ca: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
ok. In case you missed the brief discussion on -devel, I think we want to
switch to using git clone for everybody -- i.e. no more
sp
Updates:
Labels: -Patch-push Patch-needs_work
Comment #29 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
Janek identified some potential errors in the git usage with translation.
I'm review
Updates:
Labels: Patch-review
Comment #26 on issue 2092 by lilypond...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c26
Patchy the autobot says: LGTM.
___
bug-lilypond mail
Updates:
Labels: Patch-new
Comment #25 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c25
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If
Updates:
Labels: Patch-needs_work
Comment #24 on issue 2092 by lilypond...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c24
Patchy the autobot says: patch does not apply to master
Comment #23 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c23
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If $LILYPOND_GIT is unset, default of
Updates:
Labels: Patch-new
Comment #22 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c22
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If
Updates:
Labels: -Patch-review Patch-needs_work
Comment #21 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
(No comment was entered for this change.)
Updates:
Labels: Patch-review
Comment #20 on issue 2092 by lilypond...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c20
Patchy the autobot says: LGTM.
___
bug-lilypond mail
Updates:
Labels: Patch-new
Comment #19 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c19
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If
Updates:
Labels: Patch-review
Comment #18 on issue 2092 by lilypond...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c18
Patchy the autobot says: LGTM.
___
bug-lilypond mail
Comment #17 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
I'm sorry. I forgot to rebase to staging. Should be good to go now.
Carl
___
bug-lilypond
Updates:
Labels: Patch-new
Comment #16 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c16
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If
Updates:
Labels: Patch-needs_work
Comment #15 on issue 2092 by lilypond...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c15
Patchy the autobot says: sorry, I'm getting "patch does not apply". Tested
it twice.
Updates:
Labels: -Patch-new patch-new
Comment #14 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
I elected not to push this patch because of the concern about reviewing the
log.
I've now
Updates:
Labels: Patch-new
Comment #13 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c13
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If
Updates:
Labels: -Patch-countdown Patch-push
Comment #12 on issue 2092 by colinpkc...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
Counted down to 20120103, please push
___
Updates:
Labels: Patch-review
Comment #10 on issue 2092 by lilypond...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c10
Patchy the autobot says: LGTM.
___
bug-lilypond mail
Updates:
Status: Started
Comment #9 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
(No comment was entered for this change.)
___
bug-lilypond mai
Comment #8 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c8
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If $LILYPOND_GIT is unset, default of $
Comment #7 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c7
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If $LILYPOND_GIT is unset, default of $
Updates:
Labels: Patch-new
Comment #6 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c6
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If $
Comment #5 on issue 2092 by d...@gnu.org: lily-git.tcl should using
a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
We have been there already.
See http://permalink.gmane.org/gmane.comp.gnu.lilypond.devel/42253>
and preceding mails.
Comment #4 on issue 2092 by gra...@percival-music.ca: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
It's easier to explain
"do whatever you want in dev/xxx"
than
"do whatever you want, other than not using master or staging or
trans
Comment #3 on issue 2092 by d...@gnu.org: lily-git.tcl should using
a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
What's with the dev? It is inconvenient to use. I find it ok to have a
dev directory on the master repository where private stuff needing a
repo
Comment #2 on issue 2092 by gra...@percival-music.ca: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
correction: the branch should be called
dev/working
to reinforce the idea that we should keep our work in dev/foo.
___
Comment #1 on issue 2092 by gra...@percival-music.ca: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
Also, would it be possible to make lily-git.tcl use
$LILYPOND_GIT
for the download directory? lilydev will be setting that to
~/lilyp
Status: Accepted
Owner: carl.d.s...@gmail.com
Labels: Type-Maintainability
New issue 2092 by gra...@percival-music.ca: lily-git.tcl should using
a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
Strictly a change "under the hood": could lily-git.tcl put commits on its
34 matches
Mail list logo
