All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Viguera <javier.viguera@digi.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [for-dora] backport bitbake git fetcher fix
Date: Fri, 28 Feb 2014 12:07:38 +0100	[thread overview]
Message-ID: <53106DFA.6030308@digi.com> (raw)
In-Reply-To: <991B6481567A894BA8E18E29D118D85801558DEB1EF4@dor-sms-exch01.digi.com>

Hi all,

Seems that this didn't catch much attention. Maybe because this is not 
the correct list for bitbake fixes.

I had a look at bitbake git repo and they did not follow the branching 
scheme in openembedded/poky. So where do i need to send a fix for 
bitbake that i need to be included in already-released poky Dora?

-
Javier Viguera
Software Engineer
Digi International® Spain S.A.U.



On 21/02/14 17:54, Viguera, Javier wrote:
> Hi all,
>
> I'm using Dora with a customer kernel that happens to have two very
> similar branch names:
>
> af186b498eb8e39ffa419d356010d67d7fa6dee3 refs/heads/android/v3.10/master
> a094f655dc2ba623742a01dcb744ed0e8ebde3ed refs/heads/v3.10/master
>
> My custom linux recipe does the following to get 'v3.10/master' branch:
>
> KBRANCH_DEFAULT = "v3.10/master"
> KBRANCH = "${KBRANCH_DEFAULT}"
> SRC_URI = "${GIT_URL}linux-2.6.git;protocol=git;branch=${KBRANCH}"
>
> But it always fetchs the 'android/v3.10/master' branch.
>
> This seems to be already fixed in master:
>
> d21c1537b7052aa24ec56434b821fee67de33a83
>
> So could that fix be cherry-picked to Dora?
>
> Directly cherry-picking the commit does not apply cleanly so i attach
> here a reworked patch that applies to Dora.
>
> -
> Javier Viguera
> Software Engineer
> Digi International® Spain S.A.U.
>



  reply	other threads:[~2014-02-28 11:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 16:54 [for-dora] backport bitbake git fetcher fix Viguera, Javier
2014-02-28 11:07 ` Javier Viguera [this message]
2014-03-11  8:22   ` [poky] " Robert Yang
2014-03-11  8:22     ` Robert Yang

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=53106DFA.6030308@digi.com \
    --to=javier.viguera@digi.com \
    --cc=poky@yoctoproject.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 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.