On 1/2/14 9:41 AM, Carl Peterson carlopeter...@gmail.com wrote:
Just now seeing this (I don't think I was subscribed when Carl S.
wrote this). After my recent experience with lily-git.tcl and
submitting a patch, one thing I would request is that, if possible,
some kind of automatic line
On Wed, Jan 1, 2014 at 10:12 AM, James pkx1...@gmail.com wrote:
On 07/12/13 18:33, Carl Sorensen wrote:
I've thought of some possible fixes:
1) Add an expert mode button that then would open up a listbox that
would allow you to choose your branch.
2) Create a special, branch-unaware version
On 07/12/13 18:33, Carl Sorensen wrote:
On 11/29/13 12:52 PM, James pkx1...@gmail.com wrote:
1. Git checkout [branch] on the command line. That's fine I can handle
that :)
Where [branch] is going to be Staging 99% of the time (but for the case
where I whined, it was stable/2.18)
2. Then run
James pkx1...@gmail.com writes:
There are some quirks (for me) that might be easier to explain or
resolve as a 'non git-fu-er' such as:
It seems that the 'update source' button doesn't update staging, only
master, so I always have to run git checkout staging, git pull and
then merge staging
On 11/29/13 12:52 PM, James pkx1...@gmail.com wrote:
1. Git checkout [branch] on the command line. That's fine I can handle
that :)
Where [branch] is going to be Staging 99% of the time (but for the case
where I whined, it was stable/2.18)
2. Then run lily-git.tcl from the same session which
Hello,
On 29/11/13 01:47, Carl Sorensen wrote:
On 11/28/13 2:53 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
Hi,
2013/11/28 Carl Sorensen c_soren...@byu.edu:
On 11/28/13 3:33 AM, David Kastrup d...@gnu.org wrote:
It
would appear that at the current point of time, just rowing back some
Phil Holmes m...@philholmes.net writes:
From: James pkx1...@gmail.com
To: Devel lilypond-devel@gnu.org
Am i the only one using lily-git.tcl of the *active* dev team?
It's possible.
I ask because since it was changed a couple of years or so ago that
it *always* assumes you want/need to be
On 11/28/13 3:33 AM, David Kastrup d...@gnu.org wrote:
Phil Holmes m...@philholmes.net writes:
From: James pkx1...@gmail.com
To: Devel lilypond-devel@gnu.org
We have the problem that lily-git.tcl is a well-meant tool. The
people who have written and changed it are not the people using it.
Hi,
2013/11/28 Carl Sorensen c_soren...@byu.edu:
On 11/28/13 3:33 AM, David Kastrup d...@gnu.org wrote:
It
would appear that at the current point of time, just rowing back some
selected changes will already accomplish a lot.
I actually don't believe that rowing back those changes will fix
On 11/28/13 2:53 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
Hi,
2013/11/28 Carl Sorensen c_soren...@byu.edu:
On 11/28/13 3:33 AM, David Kastrup d...@gnu.org wrote:
It
would appear that at the current point of time, just rowing back some
selected changes will already accomplish a lot.
Hello,
Am i the only one using lily-git.tcl of the *active* dev team?
I ask because since it was changed a couple of years or so ago that it
*always* assumes you want/need to be on dev/local_working it really
makes it a PITA for me to work with. I've been trying to make a simple
patch this
- Original Message -
From: James pkx1...@gmail.com
To: Devel lilypond-devel@gnu.org
Sent: Wednesday, November 27, 2013 9:05 PM
Subject: LILY-GIT PITA
Hello,
Am i the only one using lily-git.tcl of the *active* dev team?
I ask because since it was changed a couple of years or so ago
12 matches
Mail list logo
