On Mar 6 06:38, Eric Blake wrote: > According to Corinna Vinschen on 3/6/2007 6:18 AM: > > 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?
Sure. Well, since it's not much work anyway, I guess I will add st_birthtime soon. > And while I'm wishing, it would be nice to have openat() and friends > [...] Adding the ...at functions correctly requires some serious changes in the path evaluation routine. Chris is revamping that stuff anyway, but it's not an easy task. > [and have I ever mentioned that it would be nice if I could get copyright > assignment from my employer?] Sigh, really. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/
