From: Michal Marek <mmarek@suse.cz>
To: Thomas Chou <thomas@wytron.com.tw>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Frysinger <vapier@gentoo.org>,
linux-kernel@vger.kernel.org, nios2-dev@sopc.et.ntust.edu.tw
Subject: Re: [PATCH] gen_init_cpio: remove leading `/' from file names
Date: Thu, 2 Dec 2010 14:30:03 +0100 [thread overview]
Message-ID: <20101202133002.GC18216@sepie.suse.cz> (raw)
In-Reply-To: <4CE49503.90607@wytron.com.tw>
On Thu, Nov 18, 2010 at 10:52:51AM +0800, Thomas Chou wrote:
> Hi Andrew and Michal,
>
> On 10/06/2010 10:51 PM, Mike Frysinger wrote:
> >On Wed, Oct 6, 2010 at 03:13, Thomas Chou wrote:
> >>When we extracted the generated cpio archive using "cpio -id" command,
> >>it complained,
> >>
> >>cpio: Removing leading `/' from member names
> >>var/run
> >>cpio: Removing leading `/' from member names
> >>var/lib
> >>cpio: Removing leading `/' from member names
> >>var/lib/misc
> >>
> >>It is worse with the latest "cpio" or "pax", which tries to overwrite
> >>the host file system with the leading '/'.
> >
> >seems to work as intended on Blackfin systems, and i cant see any
> >reason to require the leading slash, so:
> >Acked-by: Mike Frysinger<vapier@gentoo.org>
> >-mike
> >
> >
>
> Would you please review this patch? It is not clear as who should
> handle this with the MAINTAINERS.
Applied to kbuild-2.6.git#kbuild, thanks a lot.
Michal
prev parent reply other threads:[~2010-12-02 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 7:13 [PATCH] gen_init_cpio: remove leading `/' from file names Thomas Chou
2010-10-06 14:51 ` Mike Frysinger
2010-11-18 2:52 ` Thomas Chou
2010-12-02 13:30 ` Michal Marek [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=20101202133002.GC18216@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nios2-dev@sopc.et.ntust.edu.tw \
--cc=thomas@wytron.com.tw \
--cc=vapier@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox