Re: Support for st_birthtime

2007-03-26 Thread Corinna Vinschen
On Mar 26 14:10, James Youngman wrote: > On 3/26/07, Eric Blake <[EMAIL PROTECTED]> wrote: > >Corinna only replied to the cygwin list. It looks like Windows will > >populate st_birthtime with st_ctime when reading filesystems that don't > >support birthtime. Er, sorry, but I didn't say that. I s

Re: Support for st_birthtime

2007-03-26 Thread James Youngman
On 3/26/07, Eric Blake <[EMAIL PROTECTED]> wrote: Corinna only replied to the cygwin list. It looks like Windows will populate st_birthtime with st_ctime when reading filesystems that don't support birthtime. This is a bit yucky, as it adds to the problem wrongly being perpetuated by Microsoft

Re: Support for st_birthtime

2007-03-26 Thread Corinna Vinschen
On Mar 25 21:28, James Youngman wrote: > On 3/25/07, Eric Blake <[EMAIL PROTECTED]> wrote: > >And part of the joy of it being a CVS development snapshot is that I can > >give some feedback back to the cygwin developers - what would you rather > >have stat do when btime is not available for a given

Re: Support for st_birthtime

2007-03-25 Thread James Youngman
On 3/25/07, Eric Blake <[EMAIL PROTECTED]> wrote: And part of the joy of it being a CVS development snapshot is that I can give some feedback back to the cygwin developers - what would you rather have stat do when btime is not available for a given file? Set tv_sec to 0, and tv_nsec to UTIME_OM

Re: Support for st_birthtime

2007-03-25 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to James Youngman on 3/25/2007 4:13 AM: > On 3/25/07, James Youngman <[EMAIL PROTECTED]> wrote: >> > st_birthtime (for seconds), or st_birthtim (for struct timespec) >> > http://cygwin.com/ml/cygwin-cvs/2007-q1/msg00122.html > > I forgot to