Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Parthiban Nallathambi <pn@denx.de>,
	openembedded-devel@lists.openembedded.org
Cc: barathiraja@gmail.com
Subject: Re: [PATCH] [busybox]: Adjust the correct version according with patches and meta-oe
Date: Sun, 18 Mar 2018 22:10:18 -0700	[thread overview]
Message-ID: <cf67ffc0-84fc-5ed5-5826-eec9b8bffabe@gmail.com> (raw)
In-Reply-To: <20180318164919.5142-1-pn@denx.de>



On 3/18/18 9:49 AM, Parthiban Nallathambi wrote:
> Patches reffered in bbapend are with 1.24 (based on
> meta-oe 'rocko') version but the bbappend naming is
> with 1.27 (based on meta-oe 'master'.
> 
> Rename the bbappend to point to correct version of
> meta-oe rocko branch.
> 
> Signed-off-by: Parthiban Nallathambi <pn@denx.de>
> ---
>   recipes-tweaks/busybox/{busybox_1.27%.bbappend => busybox_1.24%.bbappend} | 0
>   1 file changed, 0 insertions(+), 0 deletions(-)
>   rename recipes-tweaks/busybox/{busybox_1.27%.bbappend => busybox_1.24%.bbappend} (100%)
> 
> diff --git a/recipes-tweaks/busybox/busybox_1.27%.bbappend b/recipes-tweaks/busybox/busybox_1.24%.bbappend
> similarity index 100%
> rename from recipes-tweaks/busybox/busybox_1.27%.bbappend
> rename to recipes-tweaks/busybox/busybox_1.24%.bbappend
> 

Please add [meta-openwrt] in subject, and [branchname] as well 
otherwise, I will miss it, best is to send a github pull request. we do 
not have rocko branch for meta-openwrt because we only have it working 
with master and we will create sumo branch once core layers branch out.


      parent reply	other threads:[~2018-03-19  5:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-18 16:49 [PATCH] [busybox]: Adjust the correct version according with patches and meta-oe Parthiban Nallathambi
2018-03-18 16:49 ` [meta-openwrt][PATCH] [hostapd]: Update patch based on 2.6 version Parthiban Nallathambi
2018-03-19  4:50   ` Khem Raj
2018-05-11  2:51     ` Daniel F. Dickinson
2018-03-19  5:10 ` Khem Raj [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=cf67ffc0-84fc-5ed5-5826-eec9b8bffabe@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=barathiraja@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=pn@denx.de \
    /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