public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Laszlo Ersek <lersek@redhat.com>,
	devel@edk2.groups.io,  sbsigntools@groups.io
Subject: Re: [edk2-devel] [ANNOUNCE] sbsigntools version 0.9.3 available
Date: Fri, 10 Jan 2020 07:57:08 -0800	[thread overview]
Message-ID: <1578671828.3012.2.camel@HansenPartnership.com> (raw)
In-Reply-To: <88179398-8d8d-83f7-ff19-3853721ebdc3@redhat.com>

On Fri, 2020-01-10 at 11:58 +0100, Laszlo Ersek wrote:
> On 01/09/20 19:24, James Bottomley wrote:
> > The fixes since 0.9.2 are
> > 
> >    James Bottomley (1):
> >           README: update git location and add mailing list
> > information
> >     
> >     Laszlo Ersek (1):
> >           sbvarsign: fix
> > "EFI_VARIABLE_AUTHENTICATION_2.TimeStamp.Year" assignment
> >     
> >     Steve McIntyre (1):
> >           Fix PE/COFF checksum calculation
> > 
> > The git repository is
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/jejb/sbsigntools.gi
> > t
> > 
> > The tarball release is
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/jejb/sbsigntools.gi
> > t/snapshot/sbsigntools-0.9.3.tar.gz
> > 
> > And the openSUSE build service build of various distributions is
> > here:
> > 
> > https://build.opensuse.org/package/show/home:jejb1:UEFI/sbsigntools
> 
> Awesome, thank you -- the README update is very welcome. It felt
> strange that the latest commit in Jeremy's repo was from 2012 (IIRC),
> an that I had to consult a Debian bug report for finding your repo :)

You're welcome.  While I'm setting up groups.io mailing lists, I should
probably do the same for efitools.

James


      reply	other threads:[~2020-01-10 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 18:24 [ANNOUNCE] sbsigntools version 0.9.3 available James Bottomley
2020-01-10 10:58 ` [edk2-devel] " Laszlo Ersek
2020-01-10 15:57   ` James Bottomley [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-list 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=1578671828.3012.2.camel@HansenPartnership.com \
    --to=devel@edk2.groups.io \
    /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