[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
LILY-GIT PITA
From: |
James |
Subject: |
LILY-GIT PITA |
Date: |
Wed, 27 Nov 2013 21:05:05 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 |
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 evening to a separate branch stable/2.18 for one minor tely
file and I then forget that I can then no longer just make 3 clicks and
patch, no matter where I am.
I have do some stuff I have no idea how to do to merge or rebase or
branch or some such stuff just to get a patch formed.
I've managed to screw up my LILYPOND_GIT dir twice now - headless with
merge conflicts on a load of files I have not even any interest in. It's
wasted time (and it is a wasted because I have learned nothing doing
this) and end up restoring my *whole LilyDev VM* just to get a clean set
of trees. Yes I can just download the source only but then I have to
screw about with my git config and ssh and all that jazz and it's just
easier to restore a VM from a backup frankly and then pull.
If I am the only one using this tcl utility - and I think I am.
Can someone just put it back so that it can create a patch and amend
existing commit based on the branch I am on *now* not what it thinks I
should be on?
It really has put me off making any more doc contributions because I end
up having to relearn all the git cli each time as I don't live and
breathe git and the instructions in the CG assume some broad knowledge
that I don't have. It's become a game of luck as to whether I end up
with a patch or a borked tree.
I don't develop separate branches and those that are skilled enough to
do that don't use Lily-git.tcl.
James