[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: what should patchy do for staging?
From: |
David Kastrup |
Subject: |
Re: what should patchy do for staging? |
Date: |
Fri, 11 Nov 2011 07:38:45 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) |
Graham Percival <address@hidden> writes:
> On Thu, Nov 10, 2011 at 11:56:30PM +0100, David Kastrup wrote:
>> Let's take the "David, I tested dev/staging at commit 43214314xxxxxx,
>> and it's fine" mail scenario.
>
> David, I ran Patchy, and it built commit
> cd229915fc873fdb6fd0125827452cb0ba0067a7 and it's fine.
>
> Patchy has printed out the
> -----
> push merge:
> (do this manually for debugging/testing)
> git push origin HEAD:master
> -----
>
> message, but will let you do the actual pushing if you agree that
> cd229915fc873fdb6fd0125827452cb0ba0067a7 was the right thing to
> test.
Yes, this was right to test, and if HEAD at the time Patchy suggested
pushing it was cd229915fc873fdb6fd0125827452cb0ba0067a7, it would have
done right. I am pushing it myself presently. We now know that Patchy
will not do anything imprudent if master has not moved independently.
The next scenario we can test if _only_ master has moved (in which case
it might be possible to fastforward dev/staging and test it, even though
pushing the result would be a noop). I have a patch here that is fine
enough, but have to fend for breakfast soon. Probably back in 1h20.
--
David Kastrup