All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>,
	"Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 1/4] fstests: fix group list generation for whacky test names
Date: Tue, 17 May 2022 19:10:20 -0500	[thread overview]
Message-ID: <4e7ba166-15a0-6560-da42-47c0c6ad9935@sandeen.net> (raw)
In-Reply-To: <20220517043603.GN2306852@dread.disaster.area>

On 5/16/22 11:36 PM, Dave Chinner wrote:
> On Mon, May 16, 2022 at 03:26:04PM -0700, Darrick J. Wong wrote:
...
>> Did _anyone_ actually compare the group.list output before and after
>> applying the patch?

...

> I Am Not A Happy Camper.

...

And this whole thing has made me Very Sad.

Everybody's trying to do the right thing here. Darrick's original patch
tried to ease maintainer burden with group file conflicts. Dave's patch
tried to speed it up. Zorro reviewed it, cycled it through for-next and
landed it in main in a timely manner. A problem or two remained, and now
everybody's... angry. Of course.

Can we try to just show a little more grace here? Assume good intent?
Interpret things as charitably as possible? Voice concerns calmly, and
hear them nondefensively? Accept that mistakes will happen, fix them, and
move forward? It would go a long ways to making this all a lot more fun.

I'm coming at this without most of the technical context or background
for these changes. All of the issues raised seem reasonable to me:
slowing down "make" has some drawbacks. Special requirements on lines
of bash has drawbacks too. None of this is insurmountable. Document
the specialness in the template. Make the parsing more robust, or make
it fail in a more obvious way. Spend time on yet another approach to
generate group files efficiently, if that's worth it ... I dunno.

But we've got to be able to get through relatively minor issues like
this without tempers flaring, it's just not worth it.

It's not my intent to take sides or point fingers in this particular
exchange, it's just that this dynamic has played out too many times
recently, and I really wish we could collectively do better. It's not
good for us as individuals or as a community.

-Eric

  reply	other threads:[~2022-05-18  0:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  8:59 [PATCH 0/3] fstests: more fixes Dave Chinner
2022-05-16  8:59 ` [PATCH 1/4] fstests: fix group list generation for whacky test names Dave Chinner
2022-05-16 16:20   ` Darrick J. Wong
2022-05-16 21:35     ` Dave Chinner
2022-05-16 22:26       ` Darrick J. Wong
2022-05-17  4:36         ` Dave Chinner
2022-05-18  0:10           ` Eric Sandeen [this message]
2022-05-20  1:58           ` Darrick J. Wong
2022-05-18  2:23         ` Zorro Lang
2022-05-16  8:59 ` [PATCH 2/4] xfs/148: make test debuggable Dave Chinner
2022-05-16  8:59 ` [PATCH 3/4] xfs/148: fix failure from bad shortform size assumptions Dave Chinner
2022-05-16 15:37   ` Darrick J. Wong
2022-05-16 21:40     ` Dave Chinner
2022-05-16  8:59 ` [PATCH 4/4] generic/081: don't run on DAX capable devices Dave Chinner

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=4e7ba166-15a0-6560-da42-47c0c6ad9935@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=fstests@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.