[lkml]   [2017]   [Nov]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] rdma: Add Jason as a co-maintainer
On Fri, Nov 17, 2017 at 02:45:01PM -0500, Doug Ledford wrote:

> On that point...I have my github repo tied into the 0day infrastructure,
> not the official repo. I do that because I've publicly announced that
> my github repo is a WIP repo, and that it might be rebased. That allows
> me to correct build issues by fixing up the broken patch and thereby
> keep bisectability at its highest. If you use a branch/tag on k.o for
> your 0day testing, then fixes have to be incremental and depending on
> which patch broke the build, there might be a significant segment of
> code that is no longer bisectable.

.. and this is because the k.o repo is setup to disallow force push
for each branch, so a 0 day testing branch cannot be rebased?

> > Doug will send Stephen Rothwell a note to move his for-next pull for
> > RDMA from Doug's personal directory to:
> >
> > git://
> >
> > Branch k.o/for-next
> Actually, the linux-next testing uses a tag instead of a branch. That
> allows for oddball scenarios that you might want to get testing. Say,
> for instance, that you have a for-next branch with most of your stuff,
> but you also have a separate branch that simply isn't ready to be pushed
> yet, but you still want to get some early merge analysis, then you
> create a throwaway branch, merge your for-next and this topic branch
> together, throw the for-next tag on it for a couple or three days, and
> if Stephen doesn't find anything, you're on the right path with your
> development code. Then you just reset the tag prior to pushing to
> Linus.

Makes sense, this is why I said you'll send the note, because you know
how it is setup :)


 \ /
  Last update: 2017-11-17 22:39    [W:0.080 / U:7.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site