All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] autobuild-run: add --repo option
Date: Tue, 18 Jul 2017 09:57:02 +0200	[thread overview]
Message-ID: <20170718095702.56523c1f@windsurf> (raw)
In-Reply-To: <20170717212859.12581-1-arnout@mind.be>

Hello,

On Mon, 17 Jul 2017 23:28:59 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> This option allows to specify which Buildroot git repository to clone.
> This can be useful in several situations:
> - to use a different mirror in case you don't have a good connection to
>   github;
> - for debugging this script;
> - to point to a local, patched repository you want to test.
> 
> Note that the clone/pull will use the currently checked out branch of
> the repository if it is non-bare, which is ideal for testing.
> 
> Since switching repositories may also switch branches, we use a git
> fetch/checkout sequence instead of doing a git pull. With git pull, the
> branches would be merged instead of switched. To avoid polluting the
> log with the long git message about a detached head, while still
> getting some useful output from git, pass the --detach option to
> git checkout.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

My concern about such change (which I've already expressed in the past)
is to see build results submitted to the public autobuild.b.o instance
that do not correspond to an upstream Buildroot version.

Would it be reasonable to request that if a custom repo is used, then
uploading the results to autobuild.b.o is not possible ?

Or am I too zealous about this ?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-07-18  7:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 21:28 [Buildroot] [PATCH] autobuild-run: add --repo option Arnout Vandecappelle
2017-07-18  2:45 ` Matthew Weber
2017-07-18  7:24   ` Arnout Vandecappelle
2017-07-18  7:57 ` Thomas Petazzoni [this message]
2017-07-18  8:12   ` Arnout Vandecappelle
2017-07-18  8:19     ` Thomas Petazzoni
2017-07-18  8:25       ` Arnout Vandecappelle
2017-07-18 11:46         ` Matthew Weber
2017-07-25 20:24 ` 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=20170718095702.56523c1f@windsurf \
    --to=thomas.petazzoni@free-electrons.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.