On Sun, Feb 05, 2012 at 10:43:49AM +0100, David Kastrup wrote:
> for some reason unfathomable to me, the staging patchy contains the
> following code in compile_lilypond_test.py:
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. For example, if somebody is pushing a whole
bunch of syntax changes, you definitely need the material in
patchset 1 before trying to test patchset 2.
> ### update its own master
> run("git fetch")
> run("git checkout master")
> run("git rebase origin/master")
I make no claim that this is the proper way to do it in git.
> This is a _total_ nuisance. All of the rest of staging patchy's
> operation does not meddle with the work directory of the given
> repository, does not meddle with the index, and does not meddle with
> local branches (except for the two branches maintained explicitly for
> testing). If it were not for that nonsense, one would not need an extra
> repository for staging patchy on a cron job.
ok.
Maybe it's better to make test-patches.py run based off
origin/master instead of master?
- Graham
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
