From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] infra: add the transient download mechanism
Date: Thu, 16 Jan 2020 11:03:06 +0100 [thread overview]
Message-ID: <20200116110306.5c91286b@windsurf> (raw)
In-Reply-To: <CAOf5uwmX0vdPFW9s9fC64Q7DFvQGCWdSqZy4GjEPrryy8Sa9ZA@mail.gmail.com>
On Thu, 16 Jan 2020 10:56:53 +0100
Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote:
> We are using a similar setup of Nicolas. Right now we have
> CI and reproducible build using external tools. What I would like to solve
> with buildroot is:
>
> - make the build reproducible
> - implement topic build on custom patch using CI
> - make tagging and branching easy
Could you give more details, because these items are quite vague/fuzzy,
and I don't understand from a very practical point of view what you
mean. Could you describe some example workflow, what would be your
expectation of Buildroot's behavior, etc.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-16 10:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 20:37 [Buildroot] [PATCH] infra: add the transient download mechanism Yann E. MORIN
2020-01-15 22:04 ` Michael Nazzareno Trimarchi
2020-01-16 22:36 ` Arnout Vandecappelle
2020-01-16 9:11 ` Nicolas Carrier
2020-01-16 9:31 ` Thomas Petazzoni
2020-01-16 9:56 ` Michael Nazzareno Trimarchi
2020-01-16 10:03 ` Thomas Petazzoni [this message]
2020-01-16 10:15 ` Michael Nazzareno Trimarchi
2020-01-16 15:35 ` Yann E. MORIN
2020-01-16 16:52 ` Michael Nazzareno Trimarchi
2020-01-16 10:01 ` Nicolas Carrier
2020-01-16 10:05 ` Thomas Petazzoni
2020-01-16 15:45 ` Yann E. MORIN
2020-01-16 15:29 ` Yann E. MORIN
2020-01-16 22:49 ` Arnout Vandecappelle
2020-04-08 6:39 ` Thomas Petazzoni
2020-04-08 19:27 ` Yann E. MORIN
2020-04-08 20:03 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2020-04-27 20:04 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=20200116110306.5c91286b@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.