Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/open2300: add hash file
Date: Sun, 22 Dec 2019 14:00:38 +0100	[thread overview]
Message-ID: <20191222130038.GC26395@scaer> (raw)
In-Reply-To: <CAEyMn7ap+MRO=-fUv5uH8fOvZ9_MqHc9pb0hQuHhfyfajVpNsg@mail.gmail.com>

Heiko, All,

On 2019-12-22 13:50 +0100, Heiko Thiery spake thusly:
> Am So., 22. Dez. 2019 um 12:05 Uhr schrieb Yann E. MORIN
> <yann.morin.1998@free.fr>:
> > The subversion backend would need some love for that, so if you have a
> > bit of time on your hnads, that's be nice if you could tackle it (if
> > you're interested).
> 
> If I will get the time I can take a look on. Is this implemented in
> the dl-wrapper and co? And should it be treated like the git one?

It's handled in each backend. See for example how it's done in the git
backend, in support/download/git, lines 181 thhrough 196.

Regards,
Yann E. MORIN.

> > > By the way ... what does s.b.o mean?
> >
> > Sources.Buildroot.Org, our fallback mirror:
> >
> >     http://sources.buildroot.org/
> >
> > Regards,
> > Yann E. MORIN.
> >
> > > > Regards,
> > > > Yann E. MORIN.
> > > >
> > > > --
> > > > .-----------------.--------------------.------------------.--------------------.
> > > > |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> > > > | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> > > > | +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> > > > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> > > > '------------------------------^-------^------------------^--------------------'
> >
> > --
> > .-----------------.--------------------.------------------.--------------------.
> > |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> > | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> > | +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> > '------------------------------^-------^------------------^--------------------'

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-12-22 13:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-22  8:37 [Buildroot] [PATCH] package/open2300: add hash file Heiko Thiery
2019-12-22  9:57 ` Thomas Petazzoni
2019-12-22 10:08   ` Yann E. MORIN
2019-12-22 10:56     ` Heiko Thiery
2019-12-22 11:05       ` Yann E. MORIN
2019-12-22 12:50         ` Heiko Thiery
2019-12-22 13:00           ` Yann E. MORIN [this message]
2019-12-22 11:00   ` Heiko Thiery
2019-12-22 11:07     ` Yann E. MORIN
2019-12-22 13:11 ` 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=20191222130038.GC26395@scaer \
    --to=yann.morin.1998@free.fr \
    --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