On Sun, Feb 05, 2012 at 11:31:52AM +0100, David Kastrup wrote: > Graham Percival <gra...@percival-music.ca> writes: > > > The intent is that after doing staging->master, patchy's master > > should be updated so that a later run of test-patches.py doesn't > > miss any updates. > > If test-patches.py needs a particular state of master/index, it should > cater for it by itself rather than rely on the state left by some > independent tool running asynchronously.
I don't disagree. > > Maybe it's better to make test-patches.py run based off > > origin/master instead of master? > > test-patches.py as far as I remember is _not_ run based off _either_ > origin/master or master, but rather the current _index_. Which is about > as unreliable as one can get short of just copying the work directory. I don't disagree. > One should make it clone origin/master. I don't disagree. - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
