From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Michal Suchánek" <msuchanek@suse.de>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Cc: Varun Varada <varuncvarada@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] doc: replace jargon word "impact" with "effect"/"affect"
Date: Thu, 13 May 2021 03:28:47 -0500 [thread overview]
Message-ID: <609ce33fc57e7_5a820820@natae.notmuch> (raw)
In-Reply-To: <20210513074622.GG8544@kitsune.suse.cz>
Michal Suchánek wrote:
> On Wed, May 12, 2021 at 02:42:16PM -0500, Felipe Contreras wrote:
> > If you and your wife are deciding what to eat for dinner, and you have
> > two opinions:
> >
> > 1. Whatever is fine
> > 2. I really would like pizza
> >
> > What do you think you should order?
>
> That would be the situation if you comented on the patch adding 'impact'
> before it was merged.
No analogy is perfect.
> If you want a dining metaphor for the current situation it would be more
> like
>
> 1. There are 100 people around the table eating lasagne
You are starting wrong. *Nobody* is reading the word "impact" right now,
and we are not going to swap the word in the middle of their reading.
This is a much worse analogy, and I seriously doubt you actually think
this remotely resembles the situation at hand.
--
Felipe Contreras
next prev parent reply other threads:[~2021-05-13 8:28 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 21:48 [PATCH] doc: replace jargon word "impact" with "effect"/"affect" Varun Varada
2021-04-06 9:24 ` Michal Suchánek
2021-04-06 19:36 ` Varun Varada
2021-04-06 23:01 ` Jeff King
2021-04-07 0:06 ` Varun Varada
2021-04-28 0:39 ` Varun Varada
2021-04-28 8:58 ` Michal Suchánek
2021-04-28 18:15 ` Varun Varada
2021-04-28 18:49 ` Michal Suchánek
2021-04-30 1:51 ` Varun Varada
2021-04-30 7:59 ` Michal Suchánek
2021-05-10 17:19 ` Varun Varada
2021-05-10 17:35 ` Michal Suchánek
2021-05-10 18:37 ` Varun Varada
2021-05-11 10:43 ` Michal Suchánek
2021-05-11 13:22 ` Junio C Hamano
2021-05-12 3:02 ` Felipe Contreras
2021-05-12 2:59 ` Felipe Contreras
2021-05-12 2:48 ` Felipe Contreras
2021-05-12 2:38 ` Felipe Contreras
2021-05-12 2:34 ` Felipe Contreras
2021-05-12 2:24 ` Felipe Contreras
2021-05-11 19:59 ` Felipe Contreras
2021-05-11 20:25 ` Michal Suchánek
2021-05-11 21:38 ` Varun Varada
2021-05-12 3:43 ` Felipe Contreras
2021-05-12 4:09 ` Michal Suchánek
2021-05-12 5:13 ` Felipe Contreras
2021-05-12 6:47 ` Michal Suchánek
2021-05-12 9:06 ` Felipe Contreras
2021-05-12 10:08 ` Michal Suchánek
2021-05-12 10:33 ` Michal Suchánek
2021-05-12 11:05 ` Felipe Contreras
2021-05-12 11:20 ` Michal Suchánek
2021-05-12 11:45 ` Robert P. J. Day
2021-05-12 15:19 ` Kerry, Richard
2021-05-12 16:47 ` Varun Varada
2021-05-12 17:01 ` Michal Suchánek
2021-05-12 17:32 ` Felipe Contreras
2021-05-12 18:04 ` Michal Suchánek
2021-05-12 19:42 ` Felipe Contreras
2021-05-13 7:46 ` Michal Suchánek
2021-05-13 8:28 ` Felipe Contreras [this message]
2021-05-13 8:55 ` Robert Coup
2021-05-13 9:48 ` Michal Suchánek
2021-05-13 9:59 ` Felipe Contreras
2021-05-26 23:49 ` Varun Varada
2021-05-27 11:46 ` Michal Suchánek
2021-05-27 14:08 ` Felipe Contreras
2021-05-27 14:35 ` Michal Suchánek
2021-05-27 16:43 ` Felipe Contreras
2021-06-12 23:13 ` Varun Varada
2021-06-13 11:40 ` Michal Suchánek
2021-06-13 14:06 ` Felipe Contreras
2021-06-13 16:28 ` Michal Suchánek
2021-06-13 17:12 ` Felipe Contreras
2021-05-12 22:52 ` Varun Varada
2021-05-13 6:19 ` Felipe Contreras
2021-05-12 3:21 ` Felipe Contreras
2021-05-11 19:21 ` Felipe Contreras
2021-05-11 19:57 ` Michal Suchánek
2021-05-12 3:09 ` Felipe Contreras
2021-05-12 4:11 ` Michal Suchánek
2021-05-12 5:22 ` Felipe Contreras
2021-05-12 16:39 ` Varun Varada
2021-05-13 10:40 ` Philip Oakley
2021-05-26 23:52 ` Varun Varada
2021-05-27 11:20 ` Philip Oakley
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=609ce33fc57e7_5a820820@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=varuncvarada@gmail.com \
/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.