From: Felipe Contreras <felipe.contreras@gmail.com>
To: Sebastian Schuberth <sschuberth@gmail.com>,
Theodore Ts'o <tytso@mit.edu>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
patchwork@lists.ozlabs.org
Subject: Re: Pain points in Git's patch flow
Date: Fri, 30 Apr 2021 15:45:24 -0500 [thread overview]
Message-ID: <608c6c64746b2_2cb208ee@natae.notmuch> (raw)
In-Reply-To: <CAHGBnuNrXrHUz9f8nWEdB0PoO0FeLsNpNOGgdiYmsmAD5LjTmg@mail.gmail.com>
Sebastian Schuberth wrote:
> On Tue, Apr 20, 2021 at 12:34 AM Theodore Ts'o <tytso@mit.edu> wrote:
>
> > The primary reason why the kernel uses mailing lists is because code
> > reviews are fundamentally *discussions*, and people are used to using
> > inboxes. Sure, you can have a gerrit server send e-mail notifications
>
> [...]
>
> > maintainers simply find e-mail reviews to simply be more *convenient*
> > than using gerrit. And over time, we've used other tools to track
>
> That still sounds to me as if people are stuck to what they know.
> Maintainers are "used to using inboxes'', and that's *why* they find
> e-mail reviews to be convenient.
I'm not stuck with what I know.
The reason why I use the email workflow is not because "I'm stuck" with
it, it's because I've tried every approach out there, and they are *all*
inferior.
You tell me of an approach and I will tell you all the ways in which
it's inferior to email.
If some people want to use Gerrit, and/or Patchwork on top of email,
that's fine. You can use inferior approaches if you want, just don't
force the rest of us to stop using the superior approach.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2021-04-30 20:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 6:13 Pain points in Git's patch flow Jonathan Nieder
2021-04-14 7:22 ` Bagas Sanjaya
2021-04-14 8:02 ` Junio C Hamano
2021-04-14 21:42 ` Junio C Hamano
2021-04-15 8:49 ` Denton Liu
2021-04-15 6:06 ` Junio C Hamano
2021-04-15 15:45 ` Son Luong Ngoc
2021-04-19 2:57 ` Eric Wong
2021-04-19 13:35 ` Theodore Ts'o
2021-04-21 10:19 ` Ævar Arnfjörð Bjarmason
2021-04-28 7:21 ` Eric Wong
2021-04-28 7:05 ` Eric Wong
2021-04-15 18:25 ` Atharva Raykar
2021-04-16 19:50 ` Junio C Hamano
2021-04-16 20:25 ` Junio C Hamano
2021-05-02 5:35 ` ZheNing Hu
2021-04-18 8:29 ` Sebastian Schuberth
2021-04-18 20:54 ` Ævar Arnfjörð Bjarmason
2021-04-19 2:58 ` Eric Wong
2021-04-19 5:54 ` Sebastian Schuberth
2021-04-19 6:04 ` Sebastian Schuberth
2021-04-19 8:26 ` Ævar Arnfjörð Bjarmason
2021-04-19 19:23 ` Sebastian Schuberth
2021-04-19 22:34 ` Theodore Ts'o
2021-04-20 6:30 ` Sebastian Schuberth
2021-04-20 16:37 ` Theodore Ts'o
2021-04-30 20:45 ` Felipe Contreras [this message]
2021-04-20 10:34 ` Ævar Arnfjörð Bjarmason
2021-04-19 19:36 ` Eric Wong
2021-04-19 19:49 ` Sebastian Schuberth
2021-04-19 22:00 ` Konstantin Ryabitsev
2021-05-08 2:10 ` dwh
2021-04-19 21:49 ` Konstantin Ryabitsev
2021-04-19 23:03 ` Stephen Smith
2021-05-08 2:08 ` dwh
2021-05-08 4:41 ` Bagas Sanjaya
2021-04-30 20:58 ` Felipe Contreras
2021-04-21 4:46 ` Daniel Axtens
2021-04-26 2:04 ` brian m. carlson
2021-04-26 14:24 ` Theodore Ts'o
2021-04-26 14:36 ` Ævar Arnfjörð Bjarmason
2021-04-28 7:59 ` Eric Wong
2021-04-28 22:44 ` brian m. carlson
2021-04-30 20:16 ` Felipe Contreras
2021-04-30 20:35 ` Felipe Contreras
2021-04-30 21:09 ` Felipe Contreras
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=608c6c64746b2_2cb208ee@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=patchwork@lists.ozlabs.org \
--cc=sschuberth@gmail.com \
--cc=tytso@mit.edu \
/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).