Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] dhrystone: add a hash file
Date: Thu, 03 Dec 2015 22:18:58 +0100	[thread overview]
Message-ID: <87oae7b58d.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20151203215235.08f8d18c@gmx.net> (Peter Seiderer's message of "Thu, 3 Dec 2015 21:52:35 +0100")

>>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:

Hi,

 > Hello Peter,

 > Why not append a (short) hash to the saved file for unversioned downloads?

 > e.g. dhry-c-038a7e9

This could be done, but it complicates the primary/backup site handling
(E.G. should they use the upstream name or "our" name) - The way
sources.buildroot.net is kept up to date would mean that they would need
to use "our" name.

-- 
Venlig hilsen,
Peter Korsgaard 

  reply	other threads:[~2015-12-03 21:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 12:29 [Buildroot] [PATCH 1/4] dhrystone: add a hash file Vicente Olivert Riera
2015-12-02 12:29 ` [Buildroot] [PATCH 2/4] libglu: " Vicente Olivert Riera
2015-12-17 16:21   ` Thomas Petazzoni
2015-12-02 12:29 ` [Buildroot] [PATCH 3/4] torsmo: " Vicente Olivert Riera
2015-12-17 16:23   ` Thomas Petazzoni
2015-12-17 21:34     ` Peter Korsgaard
2015-12-02 12:29 ` [Buildroot] [PATCH 4/4] whetstone: " Vicente Olivert Riera
2015-12-17 16:23   ` Thomas Petazzoni
2015-12-02 20:45 ` [Buildroot] [PATCH 1/4] dhrystone: " Peter Korsgaard
2015-12-02 21:58   ` Arnout Vandecappelle
2015-12-02 22:03   ` Yann E. MORIN
2015-12-03 10:35   ` Vicente Olivert Riera
2015-12-03 10:44     ` Thomas Petazzoni
2015-12-03 11:42       ` Peter Korsgaard
2015-12-03 20:52         ` Peter Seiderer
2015-12-03 21:18           ` Peter Korsgaard [this message]
2015-12-17 16:20 ` Thomas Petazzoni

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=87oae7b58d.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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