From: Rob Landley <rob@landley.net>
To: Michael Witten <mfwitten@gmail.com>
Cc: Jiri Kosina <trivial@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 trivial 0/7] Miscellaneous Trivialities
Date: Tue, 20 Aug 2013 19:19:37 -0500 [thread overview]
Message-ID: <1377044377.2737.87@driftwood> (raw)
In-Reply-To: <6a1db75a9ce0483b94e4c6b2989e547b-mfwitten@gmail.com> (from mfwitten@gmail.com on Tue Aug 20 17:27:53 2013)
On 08/20/2013 05:27:53 PM, Michael Witten wrote:
> On Tue, 20 Aug 2013 16:20:02 -0500, Rob Landley wrote:
> > On 08/20/2013 11:02:42 AM, Michael Witten wrote:
> >> I've been sitting on some trivial patches for a while, and I'd just
> >> like to get them out of the way.
> >>
> >> Here is the series:
> >>
> >> [1] Docs: Kconfig: For readability, offset modifiers with commas
> >> [2] Docs: Kconfig: Use consistent whitespace indentation
> >> [3] Docs: Kconfig: Clean up the radiotap documentation
> >
> > Not a single worthwhile change in any of those three.
> >
> > Excuse me:
> >
> > Not a single, worthwhile change, in any of those three.
>
> Actually, your second attempt doesn't use commas properly.
Sorry, forgot the <shatner> tags. (Or possibly <sarcasm>.)
> In any case, this is *trivial*, miscellaneous work. I do not pretend
> to be making a major contribution; this is why I sent these patches
> `To:'
>
> Jiri Kosina <TRIVIAL@kernel.org>
>
> Other people are included as some kind of courtesy, and also so that
> any change that is actually non-trivial might be caught (as with the
> `hotplug' patch).
If you were modifying the vfs would you cc the VFS maintainer as a
"courtesy" too?
> >> [4] Docs: Kconfig: `devlopers' -> `developers'
> >
> > Sure, a typo, why not.
>
> When does a series of *trivial* changes become worthwhile? What's
> wrong
> with making refinements when it costs nothing? Must one always hide
> trivial alterations inside something more substantial?
Because some people actually read the commit logs and changes that
don't do anything add noise for no benefit? (Your fourth change was a
single typo fix. The previous three changes _combined_ were less
valuable than that single typo fix. Hence asking if we really needed
three separate commits to accomplish something that didn't actually
need to be done in the first place.)
> All right. I get it; you personally don't give a damn. I certainly
> don't hold that against you. However, there *are* people who *do*
> care about such refinements, and a nasty, condescending email
> isn't going to alter our behavior.
Actually my objection is that it's not worth the churn in the commit
logs.
But yeah, why would a guy listed in MAINTAINERS as caring about the
Documentation directory pay attention to proposed changes to the
Documentation directory? Madness. I'll butt out now...
Rob
next prev parent reply other threads:[~2013-08-21 0:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 16:02 [PATCH v3 trivial 0/7] Miscellaneous Trivialities Michael Witten
2013-08-20 16:05 ` [PATCH v3 trivial 1/7] Docs: Kconfig: For readability, offset modifiers with commas Michael Witten
2013-08-20 16:05 ` [PATCH v3 trivial 2/7] Docs: Kconfig: Use consistent whitespace indentation Michael Witten
2013-08-20 16:05 ` [PATCH v3 trivial 3/7] Docs: Kconfig: Clean up the radiotap documentation Michael Witten
2013-08-20 16:05 ` [PATCH v3 trivial 4/7] Docs: Kconfig: `devlopers' -> `developers' Michael Witten
2013-08-20 16:05 ` [PATCH v3 trivial 5/7] DRM: comment: `halve' -> `half' Michael Witten
2013-08-20 16:05 ` [PATCH v3 trivial 6/7] DRM: comment: `gdm_proc_lists' -> `drm_info_lists' Michael Witten
2013-08-20 16:05 ` [PATCH v3 trivial 7/7] DRM: cleanup: Remove unused `gamma_size' Michael Witten
2013-08-20 21:20 ` [PATCH v3 trivial 0/7] Miscellaneous Trivialities Rob Landley
2013-08-20 22:27 ` Michael Witten
2013-08-21 0:19 ` Rob Landley [this message]
2013-08-21 3:32 ` Michael Witten
2013-08-21 7:04 ` Rob Landley
2013-08-21 17:24 ` Michael Witten
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=1377044377.2737.87@driftwood \
--to=rob@landley.net \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=mfwitten@gmail.com \
--cc=rdunlap@infradead.org \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox