From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Allison Collins <allison.henderson@oracle.com>,
Eric Sandeen <sandeen@redhat.com>,
Amir Goldstein <amir73il@gmail.com>,
Dave Chinner <david@fromorbit.com>,
xfs <linux-xfs@vger.kernel.org>, Eryu Guan <guaneryu@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] FS Maintainers Don't Scale
Date: Wed, 12 Feb 2020 14:36:06 -0800 [thread overview]
Message-ID: <20200212223606.GQ6874@magnolia> (raw)
In-Reply-To: <CAPcyv4gzGzgYxEDC-hjy9cy2M+V_t9VcALM3jmH=_K8XheOF-w@mail.gmail.com>
On Wed, Feb 12, 2020 at 02:19:40PM -0800, Dan Williams wrote:
> On Wed, Feb 12, 2020 at 2:07 PM Darrick J. Wong <darrick.wong@oracle.com> wrote:
> [..]
> > I've really really wanted to be able to tell people to just send a pull
> > request for large series and skip all the email patch review stuff, but
> > I'm well aware that will start a popular revolt. But maybe we can do
> > both? Is it legit to ask that if you're sending more than a simple
> > quickfix, to please push a branch somewhere so that I can just yank it
> > down and have a look? I try to do that with every series that I send, I
> > think Allison has been doing that, Christoph does it sometimes, etc.
>
> This is begging me to point out that Konstantin has automated this
> with his get-lore-mbox tool [1]. As long as the submitter uses "git
> format-patch --base..." then the tool can automate recreating a local
> branch from a mail series.
>
> [1]: https://lore.kernel.org/workflows/20200201030105.k6akvbjpmlpcuiky@chatter.i7.local/
Yes, I'm aware of the development of git-lore-mbox, but I'd rather just
pull directly from a developer's git repo than create branches on my
computer. I /already/ have my own script to extract patches and
apply/paste/staple them onto a git tree, and xfsprogs already has
scripts to automate porting of libxfs change from the kernel.
My goal here is more to change the balance of who does what work a
little bit back towards patch authors, than it is to spend less time
putting together git trees. I mean, most of you already use git already
anyway, right? :)
--D
next prev parent reply other threads:[~2020-02-12 22:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 5:25 [LSF/MM/BPF TOPIC] FS Maintainers Don't Scale Darrick J. Wong
2020-01-31 7:30 ` [Lsf-pc] " Amir Goldstein
2020-02-01 3:20 ` Allison Collins
2020-02-02 21:46 ` Dave Chinner
2020-02-09 17:12 ` Allison Collins
2020-02-12 0:21 ` NeilBrown
2020-02-12 6:58 ` Darrick J. Wong
2020-02-12 22:06 ` Darrick J. Wong
2020-02-12 22:19 ` Dan Williams
2020-02-12 22:36 ` Darrick J. Wong [this message]
2020-02-13 15:11 ` Brian Foster
2020-02-13 15:46 ` Matthew Wilcox
2020-02-16 21:55 ` Dave Chinner
2020-02-19 0:29 ` Darrick J. Wong
2020-02-19 1:17 ` Theodore Y. Ts'o
2020-02-12 23:39 ` Dave Chinner
2020-02-13 15:19 ` Brian Foster
2020-02-17 0:11 ` Dave Chinner
2020-02-17 15:01 ` Brian Foster
2020-02-12 21:36 ` Darrick J. Wong
2020-02-12 22:42 ` Darrick J. Wong
2020-02-13 10:21 ` Amir Goldstein
2020-02-07 22:03 ` Matthew Wilcox
2020-02-12 3:51 ` Theodore Y. Ts'o
2020-02-12 22:29 ` Darrick J. Wong
2020-02-12 22:21 ` Darrick J. Wong
2020-02-13 1:23 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200212223606.GQ6874@magnolia \
--to=darrick.wong@oracle.com \
--cc=allison.henderson@oracle.com \
--cc=amir73il@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=guaneryu@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).