On Fri, 2017-11-17 at 11:14 -0700, Jason Gunthorpe wrote: > On Fri, Nov 17, 2017 at 05:54:34PM +0000, Bart Van Assche wrote: > > > > * If you send an e-mail to Wu Fengguang then he will add a branch from your > > repository to his zero-day testing. This is a great way to catch build > > failures before linux-next catches these. > > Thanks
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.
> > * Any patches that will be sent to Linus must have been in the for-next
> > repository for at least a few days. Requests to add a branch to linux-next
> > should be sent to Stephen Rothwell with linux-next in Cc.
>
> Doug will send Stephen Rothwell a note to move his for-next pull for
> RDMA from Doug's personal directory to:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.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.
--
Doug Ledford <dledf...@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
signature.asc
Description: This is a digitally signed message part
