From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] whymb: Remove redundant words
Date: Thu, 28 Apr 2016 09:31:40 -0700 [thread overview]
Message-ID: <20160428163140.GK4609@linux.vnet.ibm.com> (raw)
In-Reply-To: <ed2f9c6a-eb0e-bd1e-d104-7425900bbf73@gmail.com>
On Fri, Apr 29, 2016 at 12:46:45AM +0900, Akira Yokosawa wrote:
> On 2016/04/28 23:07, Paul E. McKenney wrote:
> > On Thu, Apr 28, 2016 at 08:18:15PM +0900, Akira Yokosawa wrote:
> >> >From 53364b467603cd5ec9e1f6a12ad9377a76ebb72a Mon Sep 17 00:00:00 2001
> >> From: Akira Yokosawa <akiysw@gmail.com>
> >> Date: Thu, 28 Apr 2016 20:08:32 +0900
> >> Subject: [PATCH] whymb: Remove redundant words
> >>
> >> The sentence fixed in commit 3d3ce3673746 ("Fix now-obsolete back
> >> reference to Compaq Wizard web page") has redundant words around
> >> the citation. This commit removes them.
> >>
> >> Signed-off-by: Akira Yokosawa <akiysw@gmail.com>
> >
> > Good catch, queued!
> >
> > And no, that change wasn't one of my better efforts, was it?
> >
> > Thanx, Paul
>
> Perhaps, you shouldn't apply your own patch on your own.
> But, who else can manage the perfbook repository.
>
> Or, in cases such as this one, you could ask an ack from the person
> in reported-by. Just a suggestion.
So the following approaches seem reasonable:
1. Get an ack, as you say. I would need to put the patch on a
separate branch in the meantime, but that is eminently doable.
2. Let the person reporting the issue produce the patch.
3. Wait until I am not massively distracted to produce the patch.
These all have drawbacks. Almost like we are living in the real world!
This particular case actually worked well -- you inspected my commit,
found the problem, and submitted the patch. All is well that ends well!
Thanx, Paul
prev parent reply other threads:[~2016-04-28 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 11:18 [PATCH] whymb: Remove redundant words Akira Yokosawa
2016-04-28 14:07 ` Paul E. McKenney
2016-04-28 15:46 ` Akira Yokosawa
2016-04-28 16:31 ` Paul E. McKenney [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=20160428163140.GK4609@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=perfbook@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.