Carl Sorensen wrote:
> Here's what I recommend (I didn't used to do this, but it
> seems to be a better way to work).
>
> git branch newfeature
> git checkout newfeature
> git rebase -i master
> git rebase -I SHA1-ID-of-the-parent-of-branch-newfeature
> git checkout master
> git pull
> git cherry-p
Carl Sorensen schrieb:
On 8/22/09 12:11 PM, "Marc Hohl" wrote:
Carl Sorensen schrieb:
On 8/22/09 3:47 AM, "Marc Hohl" wrote:
[moved from -user]
According to Neil's proposals and Carl's annotations, I created a patch
to enhance the automatic polyphony:
<< ... \\ .. >> co
On 8/22/09 12:11 PM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>>
>> On 8/22/09 3:47 AM, "Marc Hohl" wrote:
>>
>>
>>> [moved from -user]
>>>
>>> According to Neil's proposals and Carl's annotations, I created a patch
>>> to enhance the automatic polyphony:
>>>
>>> << ... \\ .. >> cons
Carl Sorensen schrieb:
On 8/22/09 3:47 AM, "Marc Hohl" wrote:
[moved from -user]
According to Neil's proposals and Carl's annotations, I created a patch
to enhance the automatic polyphony:
<< ... \\ .. >> constructs can now be used within
\DrumStaff, \TabStaff and \Staff constructs, with
On 8/22/09 3:47 AM, "Marc Hohl" wrote:
> [moved from -user]
>
> According to Neil's proposals and Carl's annotations, I created a patch
> to enhance the automatic polyphony:
>
> << ... \\ .. >> constructs can now be used within
> \DrumStaff, \TabStaff and \Staff constructs, without to
> expl
[moved from -user]
According to Neil's proposals and Carl's annotations, I created a patch
to enhance the automatic polyphony:
<< ... \\ .. >> constructs can now be used within
\DrumStaff, \TabStaff and \Staff constructs, without to
explicitly inserting placeholders.
I send it as a gzipped file
