Re: we now have "lilypond" organization on GitHub

[Janek Warchoł]

2013/9/18 Janek Warchoł <address@hidden>:
> 2013/9/17 Urs Liska <address@hidden>:
>> But as far as I've understood, code doesn't get into upstream master that
>> way anyway, there is the Rietveld code review stage in between?
>> How do commits (from developers) actually end up in master?
>
> It's
> c) they are usually not pushed to any branch, unless it's a big or
> long-running change (think "Mike's skylines").  If you want to base
> some new work on a yet unmerged patch, you usually need to ask the
> author to push the branch.

or send you patchfiles if they don't have push access.

> One problem is that you usually don't see how the final commit message
> will look like

okay, "usually" was an overstatement.  But it happens noticeably often.