From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] scripts/combo-layer: checkout branch in update when pull is disabled
Date: Tue, 21 Aug 2012 14:16:21 +0100 [thread overview]
Message-ID: <3937577.neRe3uSGJP@helios> (raw)
In-Reply-To: <1345545655-14640-1-git-send-email-paul.eggleton@linux.intel.com>
On Tuesday 21 August 2012 11:40:55 Paul Eggleton wrote:
> If the user selects not to pull the component repos, at least ensure
> that the correct branch is checked out before proceeding.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> scripts/combo-layer | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/scripts/combo-layer b/scripts/combo-layer
> index 448fe71..6134e81 100755
> --- a/scripts/combo-layer
> +++ b/scripts/combo-layer
> @@ -356,6 +356,10 @@ def action_update(conf, args):
> branch = repo.get('branch', "master")
> repo_patch_dir = os.path.join(os.getcwd(), patch_dir, name)
>
> + if conf.nopull:
> + # Need to do this here as we didn't call action_pull that would
> do it otherwise + runcmd("git checkout %s" % branch, ldir)
> +
> # Step 2: generate the patch list and store to patch dir
> logger.info("Generating patches from %s..." % name)
> if dest_dir != ".":
Actually as Richard points out we don't need to be doing the checkout here -
we can just specify the branch in the one or two places where it isn't already
specified. A different patch is on its way.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-08-21 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 10:40 [PATCH] scripts/combo-layer: checkout branch in update when pull is disabled Paul Eggleton
2012-08-21 13:16 ` Paul Eggleton [this message]
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=3937577.neRe3uSGJP@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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