All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4 v0.7.0 is available
Date: Thu, 27 May 2021 09:56:25 +0200	[thread overview]
Message-ID: <CAMuHMdU5vyhHOZ7x-3d0uQqD9kSLBztaKBt9yq+pNGTmATHxCQ@mail.gmail.com> (raw)
In-Reply-To: <20210526192558.pex7tuorwqvkzxe3@nitro.local>

Hi Konstantin,

Thanks for the new release!

On Wed, May 26, 2021 at 9:26 PM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
> - b4 am will warn when it finds a message in the thread with an
>   "Obsoleted-by:" follow-up trailer. Running "git am -c" will automatically

"b4 am -c"?

>   retrieve the linked revision, so contributors can now follow-up to the
>   obsoleted revisions by sending a follow-up reply with:
>   Obsoleted-by: https://lore.kernel.org/r/new-revision-msgid

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2021-05-27  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 19:25 b4 v0.7.0 is available Konstantin Ryabitsev
2021-05-26 19:41 ` Jason Gunthorpe
2021-05-26 19:56   ` Konstantin Ryabitsev
2021-05-26 19:58     ` Konstantin Ryabitsev
2021-05-26 20:52     ` Jason Gunthorpe
2021-05-27  7:56 ` Geert Uytterhoeven [this message]
2021-05-27 12:00   ` Konstantin Ryabitsev
2021-05-27 12:05     ` Geert Uytterhoeven
2021-05-27 13:19       ` Konstantin Ryabitsev
2021-05-27 10:19 ` Greg KH

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=CAMuHMdU5vyhHOZ7x-3d0uQqD9kSLBztaKBt9yq+pNGTmATHxCQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=konstantin@linuxfoundation.org \
    --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.