From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/1] tovid: new package
Date: Wed, 08 Apr 2015 17:15:29 -0500 [thread overview]
Message-ID: <5525A881.3000404@ou.edu> (raw)
In-Reply-To: <20150405114514.355707a4@free-electrons.com>
<snip>
On 04/05/2015 04:45 AM, Thomas Petazzoni wrote:
>
> Applied, with some minor changes:
>
> Thomas
It looks like Tovid has finished moving from SVN to github.
Github Green "Latest release" button for Tovid shows:
https://github.com/tovid-suite/tovid/releases/download/v0.35.0/tovid-0.35.0.tar.gz
I could not find any indication of a hash file - does github offer them anywhere
that I'm missing? Computed the one below locally after downloading. Is sha256sum
still preferred hash for local computation?
$ sha256sum tovid-0.35.0.tar.gz
06f7cb00b213bbe83d72f4f2076b675a662697034e1d2cdc2dce987e35c827bc tovid-0.35.0.tar.gz
Are uploaded tarballs still preferred for projects on github?
Not quite sure how to submit the change over.
Steve Kenton
next prev parent reply other threads:[~2015-04-08 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 15:35 [Buildroot] [PATCH v5 1/1] tovid: new package Steve Kenton
2015-04-05 9:45 ` Thomas Petazzoni
2015-04-08 22:15 ` Steve Kenton [this message]
2015-04-08 22:31 ` Yann E. MORIN
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=5525A881.3000404@ou.edu \
--to=skenton@ou.edu \
--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