From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] openssh: bump to version 6.8p1
Date: Wed, 18 Mar 2015 09:28:05 -0300 [thread overview]
Message-ID: <55096F55.8080407@zacarias.com.ar> (raw)
In-Reply-To: <20150318122220.GD7221@tarshish>
On 03/18/2015 09:22 AM, Baruch Siach wrote:
> That's the usual convention for .hash files. But I'm fine either way.
Well we must agree on something: upstream has a pretty unusual way to
post a hash :)
(for those curious you need to base64 decode it and pipe it to hexdump
or similar).
Regards.
prev parent reply other threads:[~2015-03-18 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 10:42 [Buildroot] [PATCH v2] openssh: bump to version 6.8p1 Gustavo Zacarias
2015-03-18 11:53 ` Baruch Siach
2015-03-18 12:19 ` Gustavo Zacarias
2015-03-18 12:22 ` Baruch Siach
2015-03-18 12:28 ` Gustavo Zacarias [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=55096F55.8080407@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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