From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] file creation time
Date: Thu, 22 Jan 2009 13:21:06 -0500 [thread overview]
Message-ID: <9f210358ba4ee2e27f2d14bb3a44219f@quanstro.net> (raw)
In-Reply-To: <df49a7370901221016u6d7ec235m51883ca8a5ee6ed7@mail.gmail.com>
On Thu Jan 22 13:17:59 EST 2009, rogpeppe@gmail.com wrote:
> 2009/1/22 <lucio@proxima.alt.za>:
> > I do wonder why this field was sacrificed in the file system(s) and
> > 9P*?
>
> useful or not, traditional unix ctime never gave the creation time
> anyway - it gave inode modification time, which isn't the
> same thing at all: it's updated when you do a chmod.
will the real creation time please stand up.
- erik
next prev parent reply other threads:[~2009-01-22 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 17:39 lucio
2009-01-22 17:43 ` erik quanstrom
2009-01-22 17:50 ` lucio
2009-01-22 17:57 ` andrey mirtchovski
2009-01-22 18:08 ` erik quanstrom
2009-01-22 18:16 ` roger peppe
2009-01-22 18:20 ` lucio
2009-01-22 20:35 ` Charles Forsyth
2009-01-22 18:21 ` erik quanstrom [this message]
2009-01-22 19:31 ` Richard Miller
2009-01-22 19:54 ` erik quanstrom
2009-01-22 19:01 ` Charles Forsyth
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=9f210358ba4ee2e27f2d14bb3a44219f@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).