Re: [Xen-devel] [PATCH v6 18/20] osstest: hook FreeBSD flight into cr-daily-branch

[Roger Pau Monne <roger.pau@xxxxxxxxxx>]

On Mon, Jul 24, 2017 at 05:13:21PM +0100, Ian Jackson wrote:
> Roger Pau Monne writes ("Re: [PATCH v6 18/20] osstest: hook FreeBSD flight 
> into cr-daily-branch"):
> > On Mon, Jul 24, 2017 at 04:44:09PM +0100, Ian Jackson wrote:
> > > Roger Pau Monne writes ("[PATCH v6 18/20] osstest: hook FreeBSD flight 
> > > into cr-daily-branch"):
> > > > +       cd $repos/freebsd
> > > > +       git push $TREE_FREEBSD $revision:refs/heads/$branchcore
> > > 
> > > We don't normally call the osstest output branch for trees which are
> > > managed by someone else, "master".  Maybe we want another name ?
> > 
> > osstest-master, likewise we are going to have osstest-stable/11 if
> > that looks fine.
> 
> In other trees directly in the xenbits toplevel we call them:
>    tested/SOMETHING              (linux-pvops.git)
>    xen-tested-master             (libvirt.git)
>    osstest/frozen/XENBRANCH      (libvirt.git)
> 
> I suggest tested/$branchcore ?

Yes, that seems fine.

> Are you implying that $branchcore might be `stable/11' ?  I don't
> think we can have osstest branches with / in...

$branchcore might be stable/11, but $branch is going to be stable-11
(no '/'). As you say above osstest already uses
osstest/frozen/XENBRANCH for libvirt, so I assume it's not a problem
to have other output git branches with '/'.

> > Thanks. Would you like me to merge the next patch (the mg-anoint
> > integration) with this one?
> 
> No, it's easier this way I think.

Thanks, Roger.

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