From: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2] meta: Add support for FILESEXTRAPATHS
Date: Mon, 14 Oct 2019 12:10:44 +0530 [thread overview]
Message-ID: <20191014064044.GA6631@lightning> (raw)
In-Reply-To: <20191007093737.5coyplnujrjobtc4@yssyq.m.ilbers.de>
On Mon, Oct 07, 2019 at 11:37:38AM +0200, Baurzhan Ismagulov wrote:
> Hello Vijai Kumar,
>
> On Fri, Oct 04, 2019 at 02:15:06PM +0530, vijaikumar.kanagarajan@gmail.com wrote:
> > OE-core provides FILESEXTRAPATHS to extend the search path for
> > files and patches. This is particularly useful when you want to
> > add more files or replace existing files using bbappend.
> >
> > Bring in support for FILESEXTRAPATHS from OE-core.
>
> Thanks. What are the possibilities of adding a test case for this?
Baurzhan,
Sorry for the late reply. I was on vacation.
Is there some test suite in ISAR to test features like these? Just wondering
where would the test cases go.
Thanks,
Vijai Kumar K
>
> With kind regards,
> Baurzhan.
>
> --
> You received this message because you are subscribed to the Google Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20191007093737.5coyplnujrjobtc4%40yssyq.m.ilbers.de.
next prev parent reply other threads:[~2019-10-14 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 13:54 [PATCH] " vijaikumar.kanagarajan
2019-10-04 7:30 ` Jan Kiszka
2019-10-04 7:42 ` Vijai Kumar K
2019-10-04 8:45 ` [PATCH v2] " vijaikumar.kanagarajan
2019-10-07 9:37 ` Baurzhan Ismagulov
2019-10-14 6:40 ` Vijai Kumar K [this message]
2019-10-14 7:49 ` Jan Kiszka
2019-10-14 7:51 ` Jan Kiszka
2019-10-15 9:41 ` Vijai Kumar K
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=20191014064044.GA6631@lightning \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=isar-users@googlegroups.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