-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 08 Nov 2012 08:05:30 +0100
Jim Meyering wrote:
>
> Hmm trying the latest from gnulib, I saw a compilation failure.
> And it was my fault for omitting a hunk of your patch when
> I adjusted it. Sorry about that.
>
> Here's the fix.
>
>
Jim Meyering wrote:
> Date: Sun, 4 Nov 2012 16:41:15 -0800
> Subject: [PATCH] mountlist: do not classify a bind-mounted dir entry as
> "dummy"
>
> * lib/mountlist.c (ME_DUMMY_0): Rename from ME_DUMMY, but omit
> the "none"-testing clause.
> (ME_DUMMY) [MOUNTED_GETMNTENT1]: New macro to encapsulate
Andrew Warshall wrote:
...
> This looks fine.
I've pushed it to gnulib, so this bug will be fixed
in coreutils the next time it syncs from gnulib.
> It should (I hope) have no effect on a system w/o
> MOUNTED_GETMNTENT1; I was more concerned about the effect on anyone
> with MOUNTED_GETMNTENT1 bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 05 Nov 2012 02:01:53 +0100
Jim Meyering wrote:
> Thanks for the patch.
> However, I'd rather not duplicate all of that logic solely
> to change the part that deals with type-"none" entries.
> Instead, I'll leave the other 5 types in a separate
Andrew Warshall wrote:
>> If we went that route, we'd change how me_dummy is set so that it
>> takes account of your case. For example, we might add a boolean
>> "is_bind_mount" parameter to ME_DUMMY macro, so that when me_type is
>> "none" and is_bind_mount is true, ME_DUMMY would evaluate to fal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> If we went that route, we'd change how me_dummy is set so that it
> takes account of your case. For example, we might add a boolean
> "is_bind_mount" parameter to ME_DUMMY macro, so that when me_type is
> "none" and is_bind_mount is true, ME_DUMMY w
