From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936149AbdKQVdB (ORCPT ); Fri, 17 Nov 2017 16:33:01 -0500 Received: from mail-wr0-f194.google.com ([209.85.128.194]:46255 "EHLO mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762633AbdKQVcc (ORCPT ); Fri, 17 Nov 2017 16:32:32 -0500 X-Google-Smtp-Source: AGs4zMYmqmZ27A9+Tmfvqr8neA61A8oNZDaBPfWKdUVUSbDOHX18mn+3yCdErmQKsuSSBd2/yqq7Qw== Date: Fri, 17 Nov 2017 14:32:27 -0700 From: Jason Gunthorpe To: Doug Ledford Cc: Bart Van Assche , "linux-kernel@vger.kernel.org" , "linux-rdma@vger.kernel.org" Subject: Re: [PATCH] rdma: Add Jason as a co-maintainer Message-ID: <20171117213227.GQ4276@ziepe.ca> References: <20171116204400.GA28216@mellanox.com> <1510941272.2846.46.camel@wdc.com> <20171117181410.GL4276@ziepe.ca> <1510947901.3973.26.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1510947901.3973.26.camel@redhat.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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://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. Makes sense, this is why I said you'll send the note, because you know how it is setup :) Jason