[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190508155050.186a1ba4@lwn.net>
Date: Wed, 8 May 2019 15:50:50 -0600
From: Jonathan Corbet <corbet@....net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@...hat.com>,
cluster-devel <cluster-devel@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
"Tobin C. Harding" <me@...in.cc>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: GFS2: Pull Request
On Wed, 8 May 2019 14:05:35 -0700
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> On Wed, May 8, 2019 at 1:58 PM Jonathan Corbet <corbet@....net> wrote:
> >
> > I think this certainly belongs in the maintainer manual, but probably not
> > in pull-requests.rst. There are a lot of things about repository
> > management that seem to trip up even experienced maintainers; pre-pull
> > merges is just one of those. I would love to see a proper guide on when
> > and how to do merges in general.
>
> We had another pull request issue today, about a situation that I
> definitely know you've written about in the past, because I linked to
> lwn in my email:
>
> https://lore.kernel.org/lkml/CAHk-=wiKoePP_9CM0fn_Vv1bYom7iB5N=ULaLLz7yOST3K+k5g@mail.gmail.com/
Sigh, I never can escape my past sins...
> and while I suspect people don't actually read documentation
> (_particularly_ maintainers that have already been around for a long
> time but still do this), maybe that part could be in the same
> documentation?
Something derived from that would make sense, yes. I'll see if I can't
pull something together, unless by some delightful miracle somebody beats
me to it.
jon
Powered by blists - more mailing lists