Date: Mon, 13 Jul 2015 18:50:34 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: NGie Cooper <yaneurabeya@gmail.com>, Kirk McKusick <mckusick@FreeBSD.org> Cc: Julian Elischer <julian@FreeBSD.org>, freebsd <freebsd-hackers@FreeBSD.org> Subject: Re: Fix MNAMELEN or reimplement struct statfs Message-ID: <55A3DE4A.4050102@FreeBSD.org> In-Reply-To: <CAGHfRMCe3e8EFG9Xr8HxkpDX7dLxX_0FyRhLC7K91EDHg77mcg@mail.gmail.com> References: <20140415233133.GA14686@ambrisko.com> <5452600C.5030003@omnilan.de> <20141101154004.GA40398@ambrisko.com> <559FD426.3000108@omnilan.de> <20150710154654.GA71708@ambrisko.com> <55A33A8A.6070505@freebsd.org> <CAGHfRMCe3e8EFG9Xr8HxkpDX7dLxX_0FyRhLC7K91EDHg77mcg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13/07/2015 12:13, NGie Cooper wrote: > On Sun, Jul 12, 2015 at 9:11 PM, Julian Elischer <julian@freebsd.org> wrote: >> this hits us occasionally too >> Kirk, you are mentioned here as having a finger in this pie. >> >> do we have a suggested way forward? > > Alternatively, is the ino64_t work slated for CURRENT anytime soon (if > it was before 11.0-RELEASE that would be best probably...). > Thanks! I also would love to see MNAMELEN work in head as soon as possible. I am personally not that much interested in ino64_t, but it would be great as well. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A3DE4A.4050102>