From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/poco: bump to version 1.6.1
Date: Mon, 10 Aug 2015 16:34:09 +0200 [thread overview]
Message-ID: <1439217249.5186.18.camel@embedded.rocks> (raw)
In-Reply-To: <20150810162227.6a3cde19@free-electrons.com>
Dear Thomas Petazzoni,
On Mo, 2015-08-10 at 16:22 +0200, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Tue, 4 Aug 2015 11:57:27 +0200, J?rg Krause wrote:
> > Also:
> > * switch from sourceforge to github
> > * remove hash (github-helper)
>
> You should have actually removed the hash file entirely, so I've done
> that and applied to the next branch.
In that case I do not understand the help text from
nightly.buildroot.org, 17.4. The .hash file:
"The none hash type is reserved to those archives downloaded from a
repository, like a git clone, a subversion checkout? or archives
downloaded with the github helper Section 17.19.2, ?How to add a
^^^^^^^^^^^^^
package from GitHub?."
And from the example:
"# No hash for 1234, comes from the github-helper:
none xxx
libfoo-1234.tar.gz"
Best regards
J?rg Krause
next prev parent reply other threads:[~2015-08-10 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 9:57 [Buildroot] [PATCH 1/2] package/poco: bump to version 1.6.1 Jörg Krause
2015-08-04 9:57 ` [Buildroot] [PATCH 2/2] package/poco: disable for static build Jörg Krause
2015-08-06 6:56 ` Thomas Petazzoni
2015-08-10 14:22 ` [Buildroot] [PATCH 1/2] package/poco: bump to version 1.6.1 Thomas Petazzoni
2015-08-10 14:34 ` Jörg Krause [this message]
2015-08-10 18:54 ` Thomas Petazzoni
2015-08-10 20:47 ` Yann E. MORIN
2015-08-11 8:13 ` [Buildroot] .hash files for all packages? Thomas Petazzoni
2015-08-11 8:55 ` 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=1439217249.5186.18.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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