Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Sorgemoel <jean.sorgemoel@laposte.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] iso9660: Added support for overlay directories
Date: Thu, 27 Feb 2014 19:13:50 +0100	[thread overview]
Message-ID: <530F805E.2090906@laposte.net> (raw)
In-Reply-To: <5303A40A.1090704@barkynet.com>

>
> On 17/02/14 07:06, Arnout Vandecappelle wrote:
>> On 04/02/14 22:25, Martin Bark wrote:
>>> This patch adds a variable BR2_TARGET_ROOTFS_ISO9660_OVERLAY that
>>> is similar to BR2_ROOTFS_OVERLAY except the files are placed in the
>>> iso9660 file system.
>>>
>>> Signed-off-by: Martin Bark <martin@barkynet.com>
>>
>> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
>>
>>   I haven't tried it but it looks obviously-correct.
>>
>>   Jean Sergemoel has a patch in the queue that does a similar thing (in
>> addition to a few more changes). Jean, could you rebase your patches on
>> top of this one? And, if possible, also test if this one works for you.
>> If yes, add your Tested-by to this patch.
>
> Arnout,
>
> Thanks for the review.  Yes by some strange coincidence both Jean and 
> myself sent patches for the iso9660 file system on the same day.  I 
> agree it would be best to rebase Jeans patches.
>
>
> Jean,
>
> Let me know if you want any assistance on producing an updated patch set.
>
> Thanks
>

Hi All,

Ok, I will include that in my patch.

Regards,
Jean

  reply	other threads:[~2014-02-27 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 21:25 [Buildroot] [PATCH 1/1] iso9660: Added support for overlay directories Martin Bark
2014-02-17  7:06 ` Arnout Vandecappelle
2014-02-17 11:42   ` Mike Zick
2014-02-17 12:02     ` Arnout Vandecappelle
2014-02-18 18:18   ` Martin Bark
2014-02-27 18:13     ` Jean Sorgemoel [this message]
2014-03-01 20:59       ` jean.sorgemoel at laposte.net

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=530F805E.2090906@laposte.net \
    --to=jean.sorgemoel@laposte.net \
    --cc=buildroot@busybox.net \
    /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