Date: Sun, 4 May 2003 15:56:54 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/bin/ls extern.h ls.c print.c util.c src/bin/pax ar_io.c ar_subs.c cache.c cpio.c extern.h gen_subs.c getoldopt.c options.c pat_rep.c pax.c pax.h src/bin/ps fmt.c src/bin/rcp rcp.c Message-ID: <20030504125654.GC699@gothmog.gr> In-Reply-To: <xzpu1cbirzr.fsf@flood.ping.uio.no> References: <200305031639.h43GdYQ4049867@repoman.freebsd.org> <20030503205500.GB3907@gothmog.gr> <20030503210442.GC3907@gothmog.gr> <xzpu1cbirzr.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2003-05-04 00:29, Dag-Erling Smorgrav <des@ofug.org> wrote: > Giorgos Keramidas <keramida@ceid.upatras.gr> writes: > > - (void)strftime(buf, sizeof(buf), "%e%b%y", tp); > > + (void)strftime(buf, sizeof(buf), "%e%b%Y", tp); > > [...] > Anyway, the point is that in this case the warning is wrong. The code > is not Y2K safe but it can't be made Y2K safe without breaking the > formatting - and it doesn't even need to be Y2K safe in the first > place since the date displayed is known to lie between boottime and > timeofday so you'd have to have a 100-year uptime for it to become a > problem. Ah, thanks :) Then I should look at WARNS and why it doesn't include -Wno-format-y2k in the case of WARNS=1.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030504125654.GC699>