public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Foiani <tkil@scrye.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Enumerate the guidelines for stable patches.
Date: Fri, 30 Nov 2012 18:02:09 -0700	[thread overview]
Message-ID: <gip8m1t66.fsf@dworkin.scrye.com> (raw)
In-Reply-To: <20121201005225.GA19767@kroah.com> (Greg KH's message of "Fri, 30 Nov 2012 16:52:25 -0800")

Greg KH <gregkh@linuxfoundation.org> writes:

> Is this really needed?  For the large majority of the stable
> patches, specifically enumerating this isn't a big deal, it's a tiny
> patch, and if you think I'll remember to tell you which specific
> clause you didn't follow, then you think I have more spare time than
> I really do.

Yeah, it was largely tongue-in-cheek.  :)

Although a hint of "not upstream" would have been helpful.  You
obviously have the checklist in your head, and you (presumably) have a
your formletter automated; it just seems that, as busy as the
maintainers are, trading an extra 2s of your time for an hour of a
contributor's time would sometimes be the right thing.

Regardless, you're the one doing the work, not me.  (And you're an
outright angel, compared to some other high-level maintainers, so I
should simply count myself lucky.)

> Sorry, but no, I don't think this patch is ok, especially that S15
> clause, nice try :)

Can't fault a guy for trying.  (Or, hopefully, can't fault him much...)

Have a good weekend,
t.

      reply	other threads:[~2012-12-01  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-01  0:44 [PATCH] Documentation: Enumerate the guidelines for stable patches Anthony Foiani
2012-12-01  0:52 ` Greg KH
2012-12-01  1:02   ` Anthony Foiani [this message]

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=gip8m1t66.fsf@dworkin.scrye.com \
    --to=tkil@scrye.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox