ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: NeilBrown <neilb@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	ksummit@lists.linux.dev, outreachy@lists.linux.dev,
	kernel-janitors@vger.kernel.org
Subject: Re: KTODO automated TODO lists
Date: Tue, 24 Oct 2023 10:25:06 +0300	[thread overview]
Message-ID: <20231024072506.GC31956@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAMuHMdUku6U2EMCEXCE_K7bX2XX28P6qXq6ByWvC25C0bVhTOw@mail.gmail.com>

Hi Geert,

On Tue, Oct 24, 2023 at 09:19:26AM +0200, Geert Uytterhoeven wrote:
> On Mon, Oct 23, 2023 at 11:46 PM NeilBrown wrote:
> > On Tue, 24 Oct 2023, Andrew Morton wrote:
> > > On Thu, 19 Oct 2023 07:11:36 +0300 Dan Carpenter wrote:
> > > > Yesterday someone on my lists just sent an email looking for kernel
> > > > tasks.
> > >
> > > Well here's a task: write a bot which follows the mailing lists and
> > > sends people nastygrams if one of their emails is more than 95%(?)
> > > quoted text.
> >
> > Doesn't your email reader automatically hide most of a large quote?
> > Mine does :-)
> 
> That's part of the problem: many people don't see anymore if the
> previous email author removed irrelevant parts or not.  Until they
> want to reply...
> 
> > > It's happening significantly more lately.  Possibly because the gmail
> > > client helpfully hides quoted text.
> 
> When replying, the Gmail web interface (or Chrome?) is also very
> slow when selecting very long irrelevant parts for deletion.  And it's
> hard to predict when "Show original" and "b4 mbox && alpine -f"
> would be faster...

Get a better e-mail client ? ;-) At least with e-mail you have a choice
between different clients.

I've refrained from replying to this thread so far, as it seemed to be a
caricature of a bikeshedding discussion, but for what it's worth, I
often find myself in the opposite situation when I'm annoyed that
someone trimmed too much of the discussion in their replies.

Yes, replying to a 3000-lines patches with a full quote ana d a
Reviewed-by tag at the very bottom, without any other comment, is
annoying. On the other hand, trimming everything but the few lines to
which you reply means that it gets much more annoying to jump in the
discussion in the middle of a mail thread. There's a difference between
trimming unrelated parts, and removing related content that happens not
to be the direct subject of a particular reply.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2023-10-24  7:25 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  4:11 Dan Carpenter
2023-10-19 12:50 ` Linus Walleij
2023-10-19 13:21   ` Geert Uytterhoeven
2023-10-19 15:43     ` Liam R. Howlett
2023-10-19 16:30     ` Bird, Tim
2023-10-19 17:34       ` Dan Carpenter
2023-10-19 17:37         ` Bird, Tim
2023-10-19 17:47 ` Konstantin Ryabitsev
2023-10-23 18:49 ` Andrew Morton
2023-10-23 18:55   ` Linus Torvalds
2023-10-23 19:00     ` Geert Uytterhoeven
2023-10-23 19:17       ` Linus Torvalds
2023-10-23 19:29     ` Steven Rostedt
2023-10-23 21:31       ` Paul E. McKenney
2023-10-23 21:44         ` Tony Luck
2023-10-23 22:25           ` Paul E. McKenney
2023-10-23 19:41     ` Konstantin Ryabitsev
2023-10-24  4:58       ` Andrew Morton
2023-10-24 15:28       ` Konstantin Ryabitsev
2023-10-26 21:58         ` Miguel Ojeda
2023-10-23 21:45   ` NeilBrown
2023-10-24  7:19     ` Geert Uytterhoeven
2023-10-24  7:25       ` Laurent Pinchart [this message]
2023-10-24  8:42         ` Jani Nikula
2023-10-24  8:52           ` Laurent Pinchart
2023-10-24 12:36         ` Steven Rostedt
2023-10-24 13:12           ` Laurent Pinchart
2023-10-24 15:53   ` Krzysztof Kozlowski
2023-10-24 21:29     ` NeilBrown
2023-10-24 22:05       ` Steven Rostedt
2023-10-25  3:47         ` Paul E. McKenney
2023-10-25 23:45           ` Steven Rostedt
2023-10-25  6:55       ` Geert Uytterhoeven
2023-10-25 21:14         ` NeilBrown
2023-10-25 22:00           ` Randy Dunlap
2023-10-26  4:29           ` Dan Carpenter
2023-10-26  6:56             ` Geert Uytterhoeven
2023-10-25  7:01       ` Krzysztof Kozlowski
2023-10-25 11:45       ` James Bottomley
2023-10-25 16:40         ` Jani Nikula
2023-10-25 18:07           ` James Bottomley
2023-10-25 18:10             ` Steven Rostedt
2023-10-25 19:43               ` Linus Torvalds
2023-10-25 21:19                 ` NeilBrown
2023-10-25 21:17               ` NeilBrown
2023-10-25 18:55         ` Alexey Dobriyan
2023-10-25 19:27           ` Steven Rostedt
2023-10-25 20:03           ` Alexandre Belloni
2023-10-25 21:38         ` NeilBrown
2023-10-23 23:38 ` Gustavo A. R. Silva
2023-10-24  0:07   ` Gustavo A. R. Silva
2023-10-24  2:16   ` Joe Perches
2023-12-11 18:47   ` Steven Rostedt

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=20231024072506.GC31956@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.carpenter@linaro.org \
    --cc=geert@linux-m68k.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=neilb@suse.de \
    --cc=outreachy@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