bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1356 in lilypond: LilyPond-style comments embedded in a Scheme


From: David Kastrup
Subject: Re: Issue 1356 in lilypond: LilyPond-style comments embedded in a Scheme expression can't include special characters
Date: Mon, 28 Nov 2011 11:16:55 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux)

Graham Percival <address@hidden> writes:

> On Mon, Nov 28, 2011 at 10:54:31AM +0100, David Kastrup wrote:
>> Hm.  Should we really "verify" already when the commit made it to
>> staging?
>
> Yes.  Brief discussion was 1-3 weeks ago.
>
>> That makes the state rather arbitrary.  I'd wait at least
>> until it has migrated "properly" to master (since that's when it has
>> received its principal verification and blessing).
>
> Too hard for people with less than 5 hours of training to
> determine.

I am not sure I understand that rationale.

git log origin

Is it there or not?  Can you think of a _simpler_ test that works for
figuring out something is in _staging_?

I can't.  So what makes the verification in staging simpler than that in
master?

Note that it means _nothing_ at all if Savannah knows about the commit
id.  There are a number of possible reasons for that (for example, it
knows about something I accidentally pushed then removed again, and it
knows about everything pushed to private branches).

> If a patch made it to staging, it's not going to get lost unless
> there's a huge hue and cry about staging being broken, so that's good
> enough for me.

The huge hue and cry happens when some patch does not pass
verification...

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]