In article <20120731135245.5213217...@cvs.netbsd.org>,
Jonathan A. Kollasch wrote:
>
>Log Message:
>Use correct values for minimum and maximum cluster counts for the various FAT
>types. These values come from a publically-avaliable document of an
>infallible source that must not be named due to a
On Sun, Mar 29, 2009 at 10:47:58AM +0900, Izumi Tsutsui wrote:
> > > > Add a cast to intmax_t and use %jd to print an off_t.
> > > > Fixes at least the alpha and amd64 builds.
> > >
> > > Why not PRId64?
> >
> > It is future-safe. E.g. consider when in a few years we have to switch
> > to
jo...@britannica.bec.de wrote:
> On Sun, Mar 29, 2009 at 07:07:06AM +0900, Izumi Tsutsui wrote:
> > > Modified Files:
> > > src/sbin/newfs_msdos: newfs_msdos.c
> > >
> > > Log Message:
> > > Add a cast to intmax_t and use %jd to print an off_t.
> > > Fixes at least the alpha and amd64 builds.
>
On Sun, Mar 29, 2009 at 07:07:06AM +0900, Izumi Tsutsui wrote:
> > Modified Files:
> > src/sbin/newfs_msdos: newfs_msdos.c
> >
> > Log Message:
> > Add a cast to intmax_t and use %jd to print an off_t.
> > Fixes at least the alpha and amd64 builds.
>
> Why not PRId64?
It is future-safe. E.g.
> Modified Files:
> src/sbin/newfs_msdos: newfs_msdos.c
>
> Log Message:
> Add a cast to intmax_t and use %jd to print an off_t.
> Fixes at least the alpha and amd64 builds.
Why not PRId64?
---
Izumi Tsutsui
