From: Cornelia Huck <cohuck@redhat.com>
To: Vasily Gorbik <gor@linux.ibm.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: b4 usage
Date: Thu, 27 May 2021 18:00:09 +0200 [thread overview]
Message-ID: <20210527180009.3311781a.cohuck@redhat.com> (raw)
In-Reply-To: <your-ad-here.call-01622129150-ext-7521@work.hours>
On Thu, 27 May 2021 17:25:50 +0200
Vasily Gorbik <gor@linux.ibm.com> wrote:
> > > BTW, linux-s390@vger.kernel.org is now archived on lore and we started
> >
> > Oh, nice.
> >
> > > using b4 (https://git.kernel.org/pub/scm/utils/b4/b4.git) to pick up
> > > changes. Besides all other features, it can convert Message-Id: to Link:
> >
> > I've been using b4 to pick patches (Linux and especially QEMU) for
> > quite some time now, but never felt the need to convert Message-Id: to
> > Link:. If you prefer the Link: format, I can certainly start using that
> > for kernel patches.
>
> It's up to you, whatever you prefer. Just wanted to point out that this is
> possible now. I personally just follow what seems to be a more common practice.
>
> $ git log --grep=Link:.*lore --oneline linux/master | wc -l
> 53522
> $ git log --grep=Message-Id: --oneline linux/master | wc -l
> 1666
For QEMU, it's the other way around :)
But I'll try to use Link: for kernel patches, unless I forget.
prev parent reply other threads:[~2021-05-27 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 11:34 [PULL 0/3] vfio-ccw: some fixes Cornelia Huck
2021-05-20 11:34 ` [PULL 1/3] vfio-ccw: Check initialized flag in cp_init() Cornelia Huck
2021-05-20 11:34 ` [PULL 2/3] vfio-ccw: Reset FSM state to IDLE inside FSM Cornelia Huck
2021-05-20 11:34 ` [PULL 3/3] vfio-ccw: Serialize FSM IDLE state with I/O completion Cornelia Huck
2021-05-26 22:33 ` [PULL 0/3] vfio-ccw: some fixes Vasily Gorbik
2021-05-27 6:33 ` b4 usage (was: [PULL 0/3] vfio-ccw: some fixes) Cornelia Huck
2021-05-27 15:25 ` Vasily Gorbik
2021-05-27 16:00 ` Cornelia Huck [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=20210527180009.3311781a.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@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