From: Sam Ravnborg <sam@ravnborg.org>
To: Dave Airlie <airlied@gmail.com>
Cc: "Martin Schlemmer [c]" <azarah@nosferatu.za.org>,
Sam Ravnborg <sam@ravnborg.org>, Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.9-bk7] Select cpio_list or source directory for initramfs image updates [u]
Date: Wed, 27 Oct 2004 08:21:48 +0200 [thread overview]
Message-ID: <20041027062148.GA12123@mars.ravnborg.org> (raw)
In-Reply-To: <21d7e997041026210935b2954a@mail.gmail.com>
On Wed, Oct 27, 2004 at 02:09:34PM +1000, Dave Airlie wrote:
> If timestamp differ then initramfs_list will be updated and initramfs
> > image will be remade.
>
> please put the timestamps somewhere that don't end up in the final kernel....
initramfs_list is only an inputfile to gen_cpio. So comments in this
file will/should not end up in final image.
> My life involves reproducing complete FLASH systems at any point in
> time exactly the same as the ones I produced at the previous point in
> time, I've had to hack about 5 or 6 things in the kernel to do this,
Could you try to list the places - maybe they do not all make sense.
Sam
next prev parent reply other threads:[~2004-10-27 4:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410200849.i9K8n5921516@mail.osdl.org>
2004-10-23 12:06 ` [PATCH 2.6.9-bk7] Select cpio_list or source directory for initramfs image updates [u] Martin Schlemmer [c]
2004-10-24 10:08 ` Andrew Morton
2004-10-24 13:59 ` Martin Schlemmer [c]
2004-10-24 22:26 ` Sam Ravnborg
2004-10-26 22:12 ` Sam Ravnborg
2004-10-26 21:07 ` Martin Schlemmer [c]
2004-10-26 23:15 ` Sam Ravnborg
2004-10-26 21:36 ` Martin Schlemmer [c]
2004-10-27 4:09 ` Dave Airlie
2004-10-27 6:21 ` Sam Ravnborg [this message]
2004-10-27 4:55 ` timestamps in kernel was " Dave Airlie
2004-10-27 18:44 ` Martin Schlemmer [c]
2004-10-30 23:43 ` Sam Ravnborg
2004-10-31 10:36 ` Martin Schlemmer [c]
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=20041027062148.GA12123@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.