From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
users@linux.kernel.org, workflows@vger.kernel.org
Subject: Re: RFC: Github PR bot questions
Date: Thu, 17 Jun 2021 16:23:58 +0200 [thread overview]
Message-ID: <CANiq72kW+xsCWyhaT20a2=PUjUB59ujomaarnBrTDuYo1KEuJA@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+YoHYCKaLdZFSLqKsMz1j72i=k12FVpmSo-OyB7rCorsw@mail.gmail.com>
On Thu, Jun 17, 2021 at 11:52 AM Dmitry Vyukov <dvyukov@google.com> wrote:
>
> You don't want to accept these contributions even if you won't be able
> to tell the difference on your end? But why? This looks really
> orthogonal to a person's expertise and proficiency in software
> development. Whether that's inability to deal with email, or no desire
> to spend time on that, or just personal preferences.
Agreed -- torvalds/linux may attract a lot of spam, but the LKML also
does. Any sufficiently "famous" repo/service/ML will, after all.
> On the other hand this workflow has the potential to ensure that you
> never need to remind to run checkpatch.pl, nor spend time on writing
> code formatting comments and re-reviewing v2 because code formatting
> will be enforced, etc. So I see how this is actually beneficial for
> maintainers.
Also agreed -- it is particularly useful to teach newcomers and to
save time for maintainers having to explain things. Even if a
maintainer has a set of email templates for the usual things, it takes
time vs. not even having to read the email.
Cheers,
Miguel
next prev parent reply other threads:[~2021-06-17 14:24 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 17:18 Konstantin Ryabitsev
2021-06-16 17:24 ` Drew DeVault
2021-06-16 17:47 ` Johannes Berg
2021-06-16 17:55 ` Konstantin Ryabitsev
2021-06-16 18:13 ` Miguel Ojeda
2021-06-17 17:07 ` Serge E. Hallyn
[not found] ` <CAJhbpm_BgbSx581HU0mTCkcE28n_hRx=tv74az_mE2VBmPtrVA@mail.gmail.com>
2021-06-16 18:05 ` Konstantin Ryabitsev
2021-06-16 18:11 ` Miguel Ojeda
2021-06-16 18:22 ` Konstantin Ryabitsev
2021-06-16 18:38 ` Miguel Ojeda
2021-06-16 20:10 ` Willy Tarreau
2021-06-17 15:11 ` Konstantin Ryabitsev
2021-06-17 15:25 ` Willy Tarreau
2021-06-16 20:24 ` Linus Torvalds
2021-06-17 15:09 ` Konstantin Ryabitsev
2021-06-16 21:11 ` Rob Herring
2021-06-16 21:18 ` Stefano Stabellini
2021-06-16 21:59 ` Rob Herring
2021-06-16 22:33 ` James Bottomley
2021-06-17 14:18 ` Rob Herring
2021-06-17 14:27 ` James Bottomley
2021-06-17 6:52 ` Mauro Carvalho Chehab
2021-06-17 8:20 ` Dmitry Vyukov
2021-06-17 8:55 ` Mauro Carvalho Chehab
2021-06-17 9:33 ` Dmitry Vyukov
2021-06-17 9:52 ` Geert Uytterhoeven
2021-06-17 14:33 ` Rob Herring
2021-06-17 15:24 ` Mauro Carvalho Chehab
2021-06-17 15:38 ` Rob Herring
2021-06-17 15:45 ` Christoph Hellwig
2021-06-17 14:02 ` Rob Herring
2021-06-17 14:47 ` Konstantin Ryabitsev
2021-06-17 15:25 ` Steven Rostedt
2021-06-17 15:48 ` Christoph Hellwig
2021-06-17 15:53 ` Laurent Pinchart
2021-06-17 17:15 ` Rob Herring
2021-06-17 6:37 ` Dmitry Vyukov
2021-06-17 7:30 ` Greg KH
2021-06-17 14:59 ` Konstantin Ryabitsev
2021-06-17 8:24 ` Christoph Hellwig
2021-06-17 8:33 ` Jiri Kosina
2021-06-17 9:52 ` Dmitry Vyukov
2021-06-17 10:09 ` Christoph Hellwig
2021-06-17 14:57 ` Konstantin Ryabitsev
2021-06-17 15:16 ` Mark Brown
2021-06-17 15:24 ` Laurent Pinchart
2021-06-17 16:36 ` Geert Uytterhoeven
2021-06-17 18:43 ` Miguel Ojeda
2021-06-17 15:31 ` Paolo Bonzini
2021-06-17 17:06 ` Stefano Stabellini
2021-06-17 22:35 ` Jiri Kosina
2021-06-17 14:23 ` Miguel Ojeda [this message]
2021-06-17 20:42 ` Brendan Higgins
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='CANiq72kW+xsCWyhaT20a2=PUjUB59ujomaarnBrTDuYo1KEuJA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=dvyukov@google.com \
--cc=hch@infradead.org \
--cc=jikos@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=users@linux.kernel.org \
--cc=workflows@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox