public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Quinlan <quinlan@transmeta.com>
To: linux-kernel@vger.kernel.org
Cc: Johan Adolfsson <johan.adolfsson@axis.com>, quinlan@transmeta.com
Subject: Re: [PATCH and RFC] Compact time in cramfs
Date: Wed, 24 Apr 2002 16:51:02 -0700 (PDT)	[thread overview]
Message-ID: <15559.17638.605450.368606@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0204241009040.24998-100000@ado-2.axis.se>

Johan Adolfsson writes:

> The following patch gives a cramfs filesystem a single timestamp
> stored in the superblock. It uses the "future" field so no space is
> wasted.  mkcramfs uses the newest mtime or ctime from the
> filesystem.

Agreed, it seems like a good idea to have a filesystem timestamp.

The future field should probably be saved for use as the offset of a
"secondary superblock" (or something like that) rather than squandered
for one field.  At least, I think that was the original intent for the
field and it has always been my plan.

Maybe it would be easiest to overload the super.fsid.edition field?
Then you could have an option (probably a backward-compatible flag in
the superblock, but could be compile-time or mount-time) that indicates
that the edition number is a timestamp.

- Dan

       reply	other threads:[~2002-04-24 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0204241009040.24998-100000@ado-2.axis.se>
2002-04-24 23:51 ` Daniel Quinlan [this message]
2002-04-25  8:39   ` [PATCH and RFC] Compact time in cramfs johan.adolfsson
2002-04-23 16:26 Johan Adolfsson

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=15559.17638.605450.368606@transmeta.com \
    --to=quinlan@transmeta.com \
    --cc=johan.adolfsson@axis.com \
    --cc=linux-kernel@vger.kernel.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