Re: Draft: Extended mensural notation support

[James Lowe]

Lukas,

On 24/02/15 07:38, Werner LEMBERG wrote:
>>> To simplify the process, I suggest that you get write access to the
>>> lilypond git repository so that you can add such incremental
>>> patches to one or more separate branches (I like this method
>>> bettern than the `modern' way of forking lilypond at github, then
>>> followed by push requests) – unfortunately, with Rietveld you only
>>> see all commits squeezed to a single commit.  After a first review,
>>> you could add a new branches that replaces older ones with better
>>> commits, etc., etc.  If we have concensus, it should be easy then
>>> to merge everything into `staging'.
>>
>> Thanks for this advice. I'm afraid I have to admit I'm a total
>> novice at dealing with these kinds of versioning tools, "commits"
>> and "branches" and stuff, so I can only hope I'll manage these
>> things without messing up too much.
> 
> Don't worry, we will assist you.  If you restrict your actions to one
> or more separate branches, you won't interfere with anything else.

Or the worst case (and I don't mind helping you with this) is just give
me your changed file(s) from your own computer and I can help shepherd a
patch through with you.

This 'replace files' method is a long winded way to get changes
submitted, but I have done it this way a couple of times before for
other casual contributors (who didn't necessarily want to spend more
time learning git/our patch submission processes than was needed to make
the changes themselves).

Regards

James

P.S. If you do decide to stick with it long term, I can recommend our
'lily-git.tcl' tool (which I use all the time) that simplifies a lot of
the patch/commit making process and is documented in our Contributor's
Guide.