On Sun, 2018-01-07 at 02:01 +1100, Stephen Rothwell wrote:
> Hi Jason,
>
> On Fri, 5 Jan 2018 11:05:48 -0700 Jason Gunthorpe <jgg@xxxxxxxxxxxx> wrote:
> >
> > On Sun, Nov 19, 2017 at 02:56:33PM +1100, Stephen Rothwell wrote:
> > > Hi Doug,
> > >
> > > On Fri, 17 Nov 2017 14:47:40 -0500 Doug Ledford <dledford@xxxxxxxxxx> wrote:
> > > >
> > > > Jason Gunthorpe is now co-maintaining the RDMA subsystem with me. We
> > > > have a shared repo that we can both write into. I would like you to re-
> > > > aim the RDMA linux-next pull point to:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-
> > > > next
> > >
> > > I have updated to use this and added Jason Gunthorpe <jgg@xxxxxxxxxxxx>
> > > as a contact.
> >
> > Thanks Stephen, has been working well!
>
> No worries.
Hi Stephen,
Jason and I would like you to make another change if you could. Well,
two actually. First, we've found that now that we are both pushing to
the same tree, the use of a tag instead of a branch for your for-next
testing is dangerous. In particular, kernel git repos have a fast-
forward requirement on all branches, so an attempted push to a branch
that has stale data from the pusher (say I just managed to push to the
branch a few minutes before Jason and Jason hasn't pulled my changes
into his branch before he decides to push his) is denied by the post
hooks. But no such check is in place for tags, and indeed we are
allowed to wipe out tags at will. This has already been an accident
once, and there is no sense letting it be one again, so we've changed
our workflows to compensate for this fact, and with that change, the
for-next tag will no longer be kept up to date, it will only be pushed
when we are sending a pull request, and that's too late for testing.
From now on, the for-next branch is the canonical source going forward
for testing purposes prior to a pull request.
The second thing is we would like you to also add our for-rc branch.
Most of the time this will be a no-op, but we think there is some value
in making sure that -rc patches aren't going to cause future merge
problems with the for-next branch.
Let me know if we can do those two things. Thanks!
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDDAttachment:
signature.asc
Description: This is a digitally signed message part
