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@xxxxxxxxx>
> >> 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@xxxxxxxxx>
> >
> > 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
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
