ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	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 16:12:03 +0300	[thread overview]
Message-ID: <20231024131203.GA29036@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20231024083647.6ca474aa@gandalf.local.home>

On Tue, Oct 24, 2023 at 08:36:47AM -0400, Steven Rostedt wrote:
> On Tue, 24 Oct 2023 10:25:06 +0300 Laurent Pinchart wrote:
> 
> > 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.
> 
> After hitting "page down" 3 or 4 times and seeing only quoted text, I then
> stop and just ignore the email. Yes, there's been emails I purposely
> ignored because of this that had asked me to respond near the end. Oh well.
> Then they ask, "why didn't you respond?" pointing out the email I was to
> respond to. And I would reply, "I never saw the request because of too much
> quoted text".
> 
> > 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.
> 
> I just replied to an email yesterday that cut too much off, and I had to
> make a note about that, and put things back in.
> 
> What's worse, is if you are having a technical debate with someone, and
> they trim out everything that might go against their argument, but leave
> anything that supports their argument. I've seen that happen quite a bit.
> 
> I should write a book called "The art of trimming". ;-)

Maybe a good path forward would be to start by flagging extreme cases
only, without being too pedantic ? That assumes we can agree what an
extreme case is.

One thing I found helpful in replies is to add tags just after the
commit message (where the tag will appear when it gets applied), or
after the last comment if I need to comment on something specific. The
recipient will know that they don't need to scroll down after the tag.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2023-10-24 13:11 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
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 [this message]
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=20231024131203.GA29036@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 \
    --cc=rostedt@goodmis.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