From: Carlos Maiolino <cmaiolino@redhat.com>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Allison Henderson <allison.henderson@oracle.com>,
Brian Foster <bfoster@redhat.com>,
Catherine Hoang <catherine.hoang@oracle.com>,
Dave Chinner <david@fromorbit.com>,
Eryu Guan <guaneryu@gmail.com>,
Gao Xiang <hsiangkao@linux.alibaba.com>,
Christoph Hellwig <hch@infradead.org>,
Chandan Babu R <chandanrlinux@gmail.com>,
Eric Sandeen <sandeen@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
Bill O'Donnell <billodo@redhat.com>,
Shiyang Ruan <ruansy.fnst@fujitsu.com>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: [External] : XFS Sprints
Date: Thu, 16 Sep 2021 15:18:18 +0200 [thread overview]
Message-ID: <20210916131818.6x7bzwry76qmcjlb@andromeda.lan> (raw)
In-Reply-To: <87ee9oaeu4.fsf@debian-BULLSEYE-live-builder-AMD64>
On Thu, Sep 16, 2021 at 05:54:03PM +0530, Chandan Babu R wrote:
> > So the question I have is: Can we do community sprints? Let's get
> > together (on the lists, or irc, wherever) the week after -rc2 drops to
> > figure out who thinks they're close to submitting patchsets, decide
> > which one or two big patchsets we as a group want to try to land this
> > cycle, and then let's /all/ collaborate on making it happen. If you
> > think a cleanup would be a big help for someone else's patchset, write
> > those changes and make that part happen.
> >
> > There's never been a prohibition on us working like that, but I'd like
> > it if we were more intentional about working like a coordinated team to
> > get things done. What do you all think?
> >
> > (Small changes and bug fixes can be sent any time and I'll take a look
> > at them; I'm not proposing any changes to that part of the process.)
> >
>
> Apart from patchsets associated with implementing new features, small changes
> and bug fixes for an upcoming kernel release, may be we should also allow
> developers to post RFC patchsets to obtain an initial high-level feedback
> for a design that implements a fairly complicated new feature?
Hmm, AFAIK, this has never been a problem, just check the list, there are
several [RFC PATCH] patches around. Not sure if maybe you're talking about
something more specific?
--
Carlos
next prev parent reply other threads:[~2021-09-16 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 2:36 XFS Sprints Darrick J. Wong
2021-09-16 9:50 ` Carlos Maiolino
2021-09-16 12:24 ` [External] : " Chandan Babu R
2021-09-16 13:18 ` Carlos Maiolino [this message]
2021-09-22 14:01 ` Eric Sandeen
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=20210916131818.6x7bzwry76qmcjlb@andromeda.lan \
--to=cmaiolino@redhat.com \
--cc=allison.henderson@oracle.com \
--cc=bfoster@redhat.com \
--cc=billodo@redhat.com \
--cc=catherine.hoang@oracle.com \
--cc=chandan.babu@oracle.com \
--cc=chandanrlinux@gmail.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=guaneryu@gmail.com \
--cc=hch@infradead.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-xfs@vger.kernel.org \
--cc=ruansy.fnst@fujitsu.com \
--cc=sandeen@redhat.com \
--cc=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.