X-Spam-Check-By: sourceware.org
Message-ID: <45ED6EE6.5030509@byu.net>
Date: Tue, 06 Mar 2007 06:38:46 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: st_birthtime
References: <45ED65D9 DOT 80901 AT byu DOT net> <20070306131827 DOT GJ24859 AT calimero DOT vinschen DOT de>
In-Reply-To: <20070306131827.GJ24859@calimero.vinschen.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Corinna Vinschen on 3/6/2007 6:18 AM:
>> is it worth
>> cygwin 1.7 adding st_birthtime support?
> 
> I don't know if it's actually worth the effort, but it would be easily
> supportable in struct stat, given that we have spare room in struct stat
> of exactly the size of a timestruc_t, afaics.  But, still, does it
> really make sense?  How long will it take until st_birthtime will go
> into the standards, if at all?
> 

I don't know if any standards bodies are talking about st_birthtime.  But
imagine how useful it might be to use find(1) to find files created in a
certain time range, regardless of how their ctime has been modified since,
which is the driving factor behind the gnulib changes.  Since Windows find
can do it, why can't GNU?

And while I'm wishing, it would be nice to have openat() and friends
(which ARE being standardized for the next revision of POSIX); one of the
new functions under discussion is utimensat, which allows a standardized
way of setting file timestamps to nanosecond precision (to the granularity
supported by the file system, obviously).  A concept that was sorely
needed, since too many OS's can read sub-microsecond resolution, but
previously provided no way to set it.  Not to mention that POSIX is trying
to standardize how sub-second resolutions are reported in struct stat.
(http://www.opengroup.org/austin/docs/austin_343.html, search for Fine
Grain File Timestamps)

[and have I ever mentioned that it would be nice if I could get copyright
assignment from my employer?]

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF7W7m84KuGfSFAYARAnWPAJ9XICifpznbyFglkKRcntPJ5b3PDQCgj0C5
t+ch94DgscrLcMp0rjFqfxc=
=l58F
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/