public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: vijaikumar.kanagarajan@gmail.com, isar-users@googlegroups.com,
	jan.kiszka@siemens.com
Subject: Re: [PATCH v2 0/2] FILESEXTRAPATHS
Date: Thu, 17 Oct 2019 14:47:51 +0530	[thread overview]
Message-ID: <20191017091751.GA25819@lightning> (raw)
In-Reply-To: <20191016190536.456075c5@md1za8fc.ad001.siemens.net>

On Wed, Oct 16, 2019 at 07:05:36PM +0200, Henning Schild wrote:
> Hi Kumar,
> 
> Good idea, i guess we all stumbled over this several times ;).

Yep ;)

> 
> This deserves an entry into the RECIPE-API-CHANGELOG.md. To let people
> following that know that they can and should migrate their layers.

Sure will add and entry and send v3 for review.

Thanks,
Vijai Kumar K

> 
> Henning
> 
> Am Wed, 16 Oct 2019 20:07:43 +0530
> schrieb <vijaikumar.kanagarajan@gmail.com>:
> 
> > From: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
> > 
> > This v2 patch has the following changes.
> > 
> >  - Modify the correct bitbake.conf file.
> >  - Add a new patch to use FILESEXTRAPATHS in linux-custom.inc,
> >    u-boot-custom.inc and module.inc.
> > 
> > The second patch in the series should also hopefully serve
> > as a testcase to validate FILESEXTRAPATHS. 
> > 
> > Vijai Kumar K (2):
> >   meta: Add support for FILESEXTRAPATHS
> >   Replace FILESPATH with FILESEXTRAPATHS
> > 
> >  doc/user_manual.md                          |  2 ++
> >  meta/classes/base.bbclass                   | 19 +++++++++++++++++++
> >  meta/conf/bitbake.conf                      |  3 ++-
> >  meta/recipes-bsp/u-boot/u-boot-custom.inc   |  2 +-
> >  meta/recipes-kernel/linux-module/module.inc |  2 +-
> >  meta/recipes-kernel/linux/linux-custom.inc  |  2 +-
> >  6 files changed, 26 insertions(+), 4 deletions(-)
> > 
> 

  reply	other threads:[~2019-10-17  9:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0191015094118.GA15374@lightning>
2019-10-16 14:37 ` vijaikumar.kanagarajan
2019-10-16 14:37   ` [PATCH v2 1/2] meta: Add support for FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-16 14:37   ` [PATCH v2 2/2] Replace FILESPATH with FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-16 17:05   ` [PATCH v2 0/2] FILESEXTRAPATHS Henning Schild
2019-10-17  9:17     ` Vijai Kumar K [this message]
2019-10-17  9:28     ` [PATCH v3 " vijaikumar.kanagarajan
2019-10-17  9:28       ` [PATCH v3 1/2] meta: Add support for FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-17  9:28       ` [PATCH v3 2/2] Replace FILESPATH with FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-25 12:49       ` [PATCH v3 0/2] FILESEXTRAPATHS Baurzhan Ismagulov
2019-10-25 13:22         ` Henning Schild
2019-10-25 14:12           ` Baurzhan Ismagulov
2019-10-25 17:17             ` Jan Kiszka
2019-11-04 19:41               ` Baurzhan Ismagulov
2019-11-04 19:45       ` Baurzhan Ismagulov
2019-11-05 16:08         ` Henning Schild
2019-11-05 16:18           ` vijai kumar
2019-11-05 17:07             ` Jan Kiszka
2019-11-05 17:36               ` vijai kumar

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=20191017091751.GA25819@lightning \
    --to=vijaikumar.kanagarajan@gmail.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    /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