--b5gNqxB1S1yM7hjW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 24, 2006 at 05:04:40PM -0400, der Mouse wrote:
> >> Where do I get a suitable printf format for these types?  I seem to
> >> recall that there are macros from some include file, but can't
> >> recall enough details - PRIsomething, isn't it?
> > Right, <inttypes.h> (which gets it from machine/int_fmthio.h via
> > sys/inttypes.h):  [...example...]
>=20
> This actually turns out to not matter.  My changes don't touch any
> printf formats directly; printing is already handled, elsewhere.
>=20
> I've put a new patch into the PR (with a copy here).

I think the change is fine. However I'm wondering if it wouldn't be better=
=20
to somehow version the _ftsent structure. I doubt that du will be the only=
=20
directory-walking application that will need to deal with 64-bit values.

Take care,

Bill

--b5gNqxB1S1yM7hjW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFExnt0Wz+3JHUci9cRArHLAKCR9kqqI8wb41wkmJwMRawMTEhe4wCfaymM
GaOFZGoEbWxfaeo9fhto3BU=
=oIGf
-----END PGP SIGNATURE-----

--b5gNqxB1S1yM7hjW--