All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: [tools] b4 v0.4.0 available with new features
Date: Mon, 27 Apr 2020 14:40:51 -0400	[thread overview]
Message-ID: <20200427184051.ol7znhab6khqvjas@chatter.i7.local> (raw)
In-Reply-To: <yq1lfmkbgoi.fsf@oracle.com>

On Fri, Apr 24, 2020 at 07:35:41PM -0400, Martin K. Petersen wrote:
> 
> Hi Konstantin!
> 
> > ## b4 ty
> >
> > Allows you to automate a lot of "thanks, applied" and "thanks, merged"
> > feedback for series and pull requests that were fetched with "b4 am"
> > and "b4 pr".
> 
> I just merged a bunch of one-liners and the "thank you" quote ends up
> being:
> 
>     > Fix the following coccicheck warning:
>     > 
>     > drivers/scsi/foo/bar/baz.c
>     > 
>     > Link: https://lore.kernel.org/r/...
>     > Reported-by: ...
>     > Reviewed-by: ...
>     > Signed-off-by: ...
>     > Signed-off-by: ...
> 
> It would be nice if the quoting function could ignore the trailers
> portion of the mail and not just stuff below "---".

Yep, good point. The latest master and stable-0.4.y should do a better 
job at making these quotes. Tested on:

https://lore.kernel.org/kernel-hardening/20200229231120.1147527-1-nivedita@alum.mit.edu/

The reply generated was:

-----
On Sat, 29 Feb 2020 18:11:20 -0500, Arvind Sankar wrote:
> This currently leaks kernel physical addresses into userspace.

Applied to mricon/linux.git master, thanks!
...

-----

(Note: The reply quote is generated during the "b4 am" run, so the 
changes will only be seen on newly fetched patches/series.)

Best,
-K

  reply	other threads:[~2020-04-27 18:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 17:04 b4 v0.4.0 available with new features Konstantin Ryabitsev
2020-04-24 23:35 ` [tools] " Martin K. Petersen
2020-04-27 18:40   ` Konstantin Ryabitsev [this message]
2020-04-28  2:12     ` Martin K. Petersen
2020-04-28 15:16       ` Konstantin Ryabitsev
2020-04-29  3:25         ` Martin K. Petersen
2020-04-28 16:03       ` [kernel.org users] " Jason Gunthorpe
2020-05-04 17:09 ` [kernel.org users] " Rob Herring
2020-05-04 17:17   ` Jason Gunthorpe
2020-05-04 20:09     ` Konstantin Ryabitsev
2020-05-04 23:07       ` Jason Gunthorpe
2020-05-04 20:03   ` Konstantin Ryabitsev
2020-05-04 22:58     ` Jason Gunthorpe
2020-05-04 23:04     ` Rob Herring
2020-05-06 19:23 ` Rob Herring
2020-05-07 20:20   ` Konstantin Ryabitsev
2020-05-12 19:07     ` Rob Herring
2020-06-09 22:24       ` Rob Herring
2020-07-27 14:52         ` Konstantin Ryabitsev

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=20200427184051.ol7znhab6khqvjas@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=martin.petersen@oracle.com \
    --cc=tools@linux.kernel.org \
    --cc=users@linux.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.