From: "Johan Adolfsson" <johan.adolfsson@axis.com>
To: quinlan@transmeta.com, "Tomasz K³oczko" <kloczek@rudy.mif.pg.gda.pl>
Cc: "Daniel Quinlan" <quinlan@transmeta.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cramfs updates for 2.4.17
Date: Thu, 17 Jan 2002 11:20:06 +0100 [thread overview]
Message-ID: <18e701c19f40$88d8fdd0$0a070d0a@axis.se> (raw)
In-Reply-To: LINKIFYCbHfJdFFCfDBcbGaAcJFeFEHAdGAbJefEaDeecEJLINKIFYCBBecIcCcDfaedBbIDcFdGfGGaAGCfaAfbBbHddE <15430.14470.999605.380374@sodium.transmeta.com>
> =?ISO-8859-2?Q?Tomasz=5FK=B3oczko?= writes:
>
> > On Wed, 16 Jan 2002, Daniel Quinlan wrote:
> > [..]
> > > mkcramfs.c
> > [..]
> >
> > Why not move this tool to util-linux ?
>
> I'm actually ready to move the tools to sourceforge (the cramfs tools
> CVS tree is there).
>
> http://sourceforge.net/projects/cramfs/
>
> Assuming it's okay with Linus and Marcelo, I'll remove scripts/cramfs
> in the next version of the patch (which should be fine for 2.5 too).
>
> Dan
Why move it?
Having it in the tree makes it nice and easy to use it,
and easy keeping it in sync.
BTW: I have an improvement wish for cramfs:
Add the date of filesystemgeneration to the image header somewhere
and use that to update the time info in the inode, that way you could
get a cheap way of having some valid time stamp for the files without
it taking a lot of space (helps if you have a webserver and the browser
caches stuff)
/Johan
next prev parent reply other threads:[~2002-01-17 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 1:10 [PATCH] cramfs updates for 2.4.17 Daniel Quinlan
2002-01-17 1:20 ` Tomasz Kłoczko
2002-01-17 2:35 ` Daniel Quinlan
2002-01-17 10:20 ` Johan Adolfsson [this message]
2002-01-17 12:31 ` Erik Mouw
2002-01-17 18:54 ` Horst von Brand
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='18e701c19f40$88d8fdd0$0a070d0a@axis.se' \
--to=johan.adolfsson@axis.com \
--cc=kloczek@rudy.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=quinlan@transmeta.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