On 4/9/09 8:09 AM, "Graham Percival" <gra...@percival-music.ca> wrote:
> On Thu, Apr 09, 2009 at 03:37:39PM +0200, Simon Bailey wrote:
>> carl,
>>
>> On 9 Apr 2009, at 15:27, Carl D. Sorensen wrote:
>>> The way to get a single patch from multiple commits is to use git
>>> rebase.
>>>
>>> git rebase -i origin/master
>>>
>>> will give you the opportunity to convert your 3 commits into a single
>>> commit, which will then make a single patch.
>
> Personally, I prefer seeing multiple small patches. That said, it
> might be good to add this to the CG.
If I have three different things I am doing, then it makes sense to use
different patches.
On the other hand, if I'm doing programming work and commit changes then
find that I have a typo in my commit, it's much cleaner to rebase so that
there is only one patch.
IMO, it's not good practice to put half-baked programming patches into the
repository.
So would you like me to add this to the Contributors' Guide? I've been
restricting my work on the CG to the Programming section.
Thanks,
Carl
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
