From: Carlos Maiolino <firstname.lastname@example.org> To: Chandan Babu R <email@example.com> Cc: "Darrick J. Wong" <firstname.lastname@example.org>, Allison Henderson <email@example.com>, Brian Foster <firstname.lastname@example.org>, Catherine Hoang <email@example.com>, Dave Chinner <firstname.lastname@example.org>, Eryu Guan <email@example.com>, Gao Xiang <firstname.lastname@example.org>, Christoph Hellwig <email@example.com>, Chandan Babu R <firstname.lastname@example.org>, Eric Sandeen <email@example.com>, Matthew Wilcox <firstname.lastname@example.org>, Bill O'Donnell <email@example.com>, Shiyang Ruan <firstname.lastname@example.org>, xfs <email@example.com> Subject: Re: [External] : XFS Sprints Date: Thu, 16 Sep 2021 15:18:18 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (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 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [External] : XFS Sprints' \ /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
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).