[Top][All Lists]

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

Re: [Lilypond-auto] Patchy email

From: David Kastrup
Subject: Re: [Lilypond-auto] Patchy email
Date: Tue, 17 Jul 2012 22:33:54 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux)

David Kastrup <address@hidden> writes:

> Please _don't_ ever push a "fix" on top of a broken staging branch.  We
> want to keep master compiling always.  If your fix works, it means that
> Patchy will move both the broken commit as well as the fix to master.
> I've cleared both for now and hope that no Patchy has already picked the
> "fix" up.  I'll investigate what to do here.
> It is not quite clear to me how the bug went through my tests, and why
> Patchy does not complain (apparently make doc does not compile the "new"
> snippets ?!?).
> So we already have one fishy commit in master, but at least it is "make
> doc" clean.

Pushed a fix to staging on top of master and cleared out your changes
(after moving them to a private branch so that they don't get lost).
Let's see what commit Patchy moves to master next, and go from there.

David Kastrup

reply via email to

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