mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail.com>
To: Rob Landley <rob@landley.net>
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: Wed, 21 Aug 2013 03:32:02 -0000	[thread overview]
Message-ID: <0f201a86cef14399a093518c2743856f-mfwitten@gmail.com> (raw)
In-Reply-To: <1377044377.2737.87@driftwood>

On Tue, 20 Aug 2013 19:19:37 -0500, Rob Landley wrote:

> 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.)
> ...
> Actually my objection is that it's not worth the churn in the commit logs.

Naturally, we don't NEED three separate commits! Squash all of them
into one commit if that's something worth hissing about.

Do you need help with the relevant commands?

Because you are the former and current maintainer of large and active
projects, I'd expect you to *appreciate* the value of taking in
fine-grained patches for REVIEW (even if you don't appreciate their
sum total).

The patches have been written in a way to *ease* the job of the
maintainer in understanding the changes. The fact that you find each
patch ludicrously trivial is a GREAT sign, especially considering
that I sent them mainly to the maintainer of... *TRIVIAL* changes.

> 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...

Madness is thinking that it means something to have your name listed in
some file. You are the maintainer when people send you patches and pull
from your repo---that is, when people *like* working with you. That's it.
A name in a file is simply a starting point for those contributors who
may not know any better.

Don't take "your" position for granted.

  reply	other threads:[~2013-08-21  3:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 16:02 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
2013-08-21  3:32       ` Michael Witten [this message]
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=0f201a86cef14399a093518c2743856f-mfwitten@gmail.com \
    --to=mfwitten@gmail.com \
    --cc=airlied@linux.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rob@landley.net \
    --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

Powered by JetHome