From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] infra: add the transient download mechanism
Date: Wed, 28 Oct 2020 18:50:04 +0100 [thread overview]
Message-ID: <20201028175004.GJ2805@scaer> (raw)
In-Reply-To: <20200930223142.681174c0@windsurf.home>
Thomas, All,
On 2020-09-30 22:31 +0200, Thomas Petazzoni spake thusly:
> On Wed, 30 Sep 2020 22:13:03 +0200
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > I think it is important to stress that, though, because people can be
> > very confused but the outcome, one way or the other.
[--SNIP--]
> I understand what you're describing here, and I understand that it
> indeed should be explained. Then, it shouldn't be presented as a
> "pitfall", but really as an explanation of the consequences.
So I thought again about this, and I stand by my position.
I do not want to play down the issues attached to that (mis)feature, and
I still think this is a pitfall. So, I am not going to change the wording.
Feel free to grab the patch and adapt if you feel strongly about it.
Thanks! :-)
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-10-28 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 17:30 [Buildroot] [PATCHv2] infra: add the transient download mechanism Yann E. MORIN
2020-09-30 19:45 ` Thomas Petazzoni
2020-09-30 20:13 ` Yann E. MORIN
2020-09-30 20:31 ` Thomas Petazzoni
2020-10-28 17:50 ` Yann E. MORIN [this message]
2020-10-06 18:43 ` Arnout Vandecappelle
2020-10-28 17:56 ` 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=20201028175004.GJ2805@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