[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190524165301.GD16845@ziepe.ca>
Date: Fri, 24 May 2019 13:53:01 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Christoph Hellwig <hch@...radead.org>, akpm@...ux-foundation.org,
Dave Airlie <airlied@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jerome Glisse <jglisse@...hat.com>,
linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
Leon Romanovsky <leonro@...lanox.com>,
Doug Ledford <dledford@...hat.com>,
Artemy Kovalyov <artemyko@...lanox.com>,
Moni Shoua <monis@...lanox.com>,
Mike Marciniszyn <mike.marciniszyn@...el.com>,
Kaike Wan <kaike.wan@...el.com>,
Dennis Dalessandro <dennis.dalessandro@...el.com>,
linux-mm@...ck.org, dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: RFC: Run a dedicated hmm.git for 5.3
On Fri, May 24, 2019 at 06:27:09PM +0200, Daniel Vetter wrote:
> Sure topic branch sounds fine, we do that all the time with various
> subsystems all over. We have ready made scripts for topic branches and
> applying pulls from all over, so we can even soak test everything in our
> integration tree. In case there's conflicts or just to make sure
> everything works, before we bake the topic branch into permanent history
> (the main drm.git repo just can't be rebased, too much going on and too
> many people involvd).
We don't rebase rdma.git either for the same reasons and nor does
netdev
So the usual flow for a shared topic branch is also no-rebase -
testing/etc needs to be done before things get applied to it.
Cheers,
Jason
Powered by blists - more mailing lists