Re: b4 usage (was: [PULL 0/3] vfio-ccw: some fixes)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > BTW, linux-s390@xxxxxxxxxxxxxxx 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


> > 
> > Hm, and b4 also now complains:
> > ✗ BADSIG: DKIM/ibm.com
> > have to look into that...

Ok, figured out that this is only failing with the company vpn. Internal
dns servers handle ibm.com domain, but fail to serve public key via
"pp1._domainkey.ibm.com" request, which is required to verify DKIM.
All works fine with external dns.



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux