From: Dan Carpenter <error27@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Coping with the new-developer flood
Date: Thu, 6 Aug 2026 13:10:34 +0300 [thread overview]
Message-ID: <anRdmjsn4_2aavcx@stanley.mountain> (raw)
In-Reply-To: <87y0ekm9nw.fsf@trenco.lwn.net>
A lot of first time developers start in driver/staging where I review
patches. I had to re-edit my "How to Send a v2" instructions to
really emphasize not to resend a patch series that same day. Otherwise
it feels like you are pair programming instead of a reviewer.
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
regards,
dan carpenter
next prev parent reply other threads:[~2026-08-06 10:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 23:26 [MAINTAINERS SUMMIT] Coping with the new-developer flood Jonathan Corbet
2026-08-06 9:24 ` Matthieu Baerts
2026-08-06 10:10 ` Dan Carpenter [this message]
2026-08-06 15:42 ` Theodore Tso
2026-08-06 15:57 ` Greg KH
2026-08-06 17:28 ` Konstantin Ryabitsev
2026-08-06 18:56 ` Shuah Khan
2026-08-06 19:32 ` Dan Carpenter
2026-08-06 21:14 ` Mark Brown
2026-08-07 3:23 ` Theodore Tso
2026-08-07 9:20 ` Matthieu Baerts
2026-08-07 11:56 ` Laurent Pinchart
2026-08-07 12:28 ` James Bottomley
2026-08-07 12:40 ` Laurent Pinchart
2026-08-07 12:47 ` Arnaldo Carvalho de Melo
2026-08-07 13:36 ` Laurent Pinchart
2026-08-07 13:56 ` Rafael J. Wysocki (Intel)
2026-08-07 16:38 ` Miguel Ojeda
2026-08-07 12:51 ` James Bottomley
2026-08-07 13:34 ` Laurent Pinchart
2026-08-07 13:42 ` Mark Brown
2026-08-07 13:02 ` Mimi Zohar
2026-08-07 13:12 ` Dan Carpenter
2026-08-07 16:37 ` Miguel Ojeda
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=anRdmjsn4_2aavcx@stanley.mountain \
--to=error27@gmail.com \
--cc=corbet@lwn.net \
--cc=ksummit@lists.linux.dev \
/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