Re: [Xen-devel] [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how 
up to date each branch is"):
> Should it not be:
> 
> BRANCHES=all-branch-statuses ./cr-for-branches . -w ./cr-maintjobs ''
> which ends up calling
> ./cr-maintjobs all-branch-status
> which in turn calls (from a "case $1") the new mg- from this patch?

We probably don't need one tree for each maintenance job.  Here the
value in BRANCHES corresponds to a for-THING.git.

> Would using ~osstest/daemons-testing.git for this be an intolerable
> bodge?

Yes.  We don't want to update that without some care.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel