Carl Sorensen wrote Monday, August 24, 2009 1:25 AM
From: Trevor Daniels [t.dani...@treda.co.uk]
Not sure these rebases are necessary if
you are going to use cherrypick rather
than merge.
Yes, your method works OK.
I use the rebase to get all of my work into
a single commit, instead of having multiple
commits to cherry-pick.
Ah, right. I use the 'Amend last commit' radio
button in git gui to group my changes together
as I go. I usually save my edits-so-far with
a commit message "in progress", then click the
Amend button whenever I resume.
But you have far more complicated commits than
I do, so you probably need several separate
commits.
It seems that git, like perl, has the
implicit slogan TMTOWTDI (There's more than
one way to do it).
Indeed. We all find whichever way we're most
comfortable with. It's good to exchange ideas
though.
Carl
Trevor
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
