9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] create() and mtime
Date: Thu, 23 Oct 2003 12:38:01 +0200	[thread overview]
Message-ID: <da524aa419cd9311e0c3c2dd2fc08753@plan9.escet.urjc.es> (raw)
In-Reply-To: <2457b115760b955da8e1e96de8434eea@plan9.bell-labs.com>

[-- Attachment #1: Type: text/plain, Size: 139 bytes --]

I was not sure of the correct behaviour, so I couldnt fix it.
For me it was not clear if it was a feature or not.

Thanks for the fix.

[-- Attachment #2: Type: message/rfc822, Size: 2313 bytes --]

From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] create() and mtime
Date: Wed, 22 Oct 2003 14:56:41 -0400
Message-ID: <2457b115760b955da8e1e96de8434eea@plan9.bell-labs.com>

On Wed Oct 22 14:08:39 EDT 2003, r@geekmail.cc wrote:
> > It looks like a create of an existing file is not updating mtime. As a result
> > news prints old news because the mtime of $home/lib/newstime gets fixed to
> > the actual creation (not truncation) time.
>
> i just noticed this myself.  you need to write to a file to get its mtime updated.
> i believe this is a mistake; the manual says mtime is time of change of content,
> not time of write.
>
> i would change your news program to create and write a byte.
>
> -rob

i would fix the bug. new version of /sys/src/cmd/fossil/file.c on sources.

--jim

      reply	other threads:[~2003-10-23 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 17:46 Fco.J.Ballesteros
2003-10-22 18:06 ` rob pike, esq.
2003-10-22 18:56   ` jmk
2003-10-23 10:38     ` Fco.J.Ballesteros [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=da524aa419cd9311e0c3c2dd2fc08753@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --cc=9fans@cse.psu.edu \
    /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).