Phil Holmes m...@philholmes.net writes:
If I could have worked out how to split them, while at the same time
being able to keep track of what changes were still needed, I would
have done. However, doing things like having a screech-boink.ly in
new, with a screech-and-boink.ly in snippets, and
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
We use the staging branch exactly to avoid having to revert stuff.
Instead we reset staging. Only stuff that percolated to master needs to
get reverted in order to remove it.
--
David Kastrup
What's
Phil Holmes m...@philholmes.net writes:
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
We use the staging branch exactly to avoid having to revert stuff.
Instead we reset staging. Only stuff that percolated to master needs to
get reverted in
Both done - closing issues on Rietveld and adding 2310 to Rietveld's title.
On 3 April 2012 04:00, Colin Campbell c...@shaw.ca wrote:
Tools which we have written for the purpose are aware of the two
unconnected sources of information about patches and have been modified to
allow you to refer
On Tue, Apr 10, 2012 at 2:58 PM, Łukasz Czerwiński milimet...@gmail.com wrote:
Shouldn't git cl be rewritten to change the title of Rietveld issue to
include Google Code's issue numer?
sure, go ahead.
I don't have time because of gsoc.
cheers,
Janek
For 20:00 MDT Thursday April 12
Enhancement:
Issue 2470
http://code.google.com/p/lilypond/issues/detail?id=2470: Patch:
introduce completionUnit - R5987060
http://codereview.appspot.com/5987060/
Issue 2427
http://code.google.com/p/lilypond/issues/detail?id=2427: Patch: Add an
On Wed, Apr 11, 2012 at 2:36 AM, Colin Hall colingh...@gmail.com wrote:
On Sat, Apr 07, 2012 at 05:32:28PM +0200, Karol Majewski wrote:
Is it possible to mark 2368 bug as critical? I think this kind of
regression is a serious problem. Just take a look at my last
comment:
