From: Vagrant Cascadian <vagrant-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: DTC v1.4.6 released
Date: Sun, 21 Jan 2018 14:03:26 -0800 [thread overview]
Message-ID: <87k1wauaxd.fsf@aikidev.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
On 2018-01-04, David Gibson wrote:
> Hi everyone. There have been a number of useful bugfixes added to the
> dtc tree since v1.4.5, so I decided to tag another release.
Thanks for all the work on dtc!
> The signed tag is in the master git tree at:
>
> git://git.kernel.org/pub/scm/utils/dtc/dtc.git
I'm not seeing a signed tag for v1.4.6, and it doesn't appear in the web
interface either:
https://git.kernel.org/pub/scm/utils/dtc/dtc.git/refs/tags
> Or you can download tarballs from:
>
> https://www.kernel.org/pub/software/utils/dtc/
Fortunately, commit:e54388015af1fb4bf04d0bca99caba1074d9cc42 appears to
be consistent with the contents of the 1.4.6 tarballs.
On a related note, I was wondering if it would be possible to have the
compressed tarballs have their own signature:
https://www.kernel.org/pub/software/utils/dtc/dtc-1.4.6.tar.sign
Only validates against the uncompressed tarball, which makes
verification of the signature a bit more complicated, having to
decompresss the tarball before verification.
It also means I can not include the signature file in the Debian
archive, as the signature needs to verify against the compressed tarball
in the Debian archive. For this reason especially, it would be nice to
have dtc-X.Y.Z.tar.xz.sign available as well.
Thanks for considering!
Please CC me in replies; I'm not subscribed to the list.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2018-01-21 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 22:03 Vagrant Cascadian [this message]
[not found] ` <87k1wauaxd.fsf-LkDtOWtB3X7R7s880joybQ@public.gmane.org>
2018-01-21 23:44 ` DTC v1.4.6 released David Gibson
-- strict thread matches above, loose matches on Subject: below --
2018-01-04 3:03 David Gibson
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=87k1wauaxd.fsf@aikidev.net \
--to=vagrant-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.