----- Original Message -----
From: "Graham Percival" <gra...@percival-music.ca>
To: "Phil Holmes" <m...@philholmes.net>
Cc: <lilypond-devel@gnu.org>; "David Kastrup" <d...@gnu.org>
Sent: Monday, January 30, 2012 1:40 PM
Subject: Re: somebody needs to run staging before 29 Jan
On Mon, Jan 30, 2012 at 01:35:24PM -0000, Phil Holmes wrote:
Original Message ----- From: "David Kastrup" <d...@gnu.org>
To: <lilypond-devel@gnu.org>
Sent: Monday, January 30, 2012 1:07 PM
Subject: Re: somebody needs to run staging before 29 Jan
>Nope. It uses whatever repository you specify in the LILYPOND_GIT
>environment variable.
But if I rely on other uses for the LILYPOND_GIT environment
variable, then it must use my normal git stash. Strikes me it would
be safer to have a duplicate stash just for patchy, and a different
variable.
Yes, I have patchy on a completely separate user.
OK - just set one up and trying a test build.
My other current concern is to wonder whether lots of people trying to get
patchy running might not collide with each other. As I understand it, the
key patchy function is to pull patches from staging, run make and make test,
and check the regtest output. If this is OK it sends a message saying
"LGTM". Is this correct? Does it actually do any of the merging of patches
from staging into master? I wouldn't want to do that without knowing I was
doing it... (although my new user would presumably fail anyway, since I've
not yet set it up for push access).
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
