diff for duplicates of <20090122161104.GF9732@hack.private> diff --git a/a/1.txt b/N1/1.txt index 60839ea..d348cef 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,24 +1,21 @@ On Wed, Jan 21, 2009 at 10:04:08AM -0500, Chris Mason wrote: ->On Mon, 2009-01-19 at 21:12 +0800, Am=C3=A9rico Wang wrote: +>On Mon, 2009-01-19 at 21:12 +0800, Américo Wang wrote: >> On Mon, Jan 19, 2009 at 08:03:37AM -0500, Josef Bacik wrote: ->> >On Mon, Jan 19, 2009 at 08:57:32PM +0800, Am=C3=A9rico Wang wrote: ->> >>=20 +>> >On Mon, Jan 19, 2009 at 08:57:32PM +0800, Américo Wang wrote: +>> >> >> >> I found userspace tool, btrfsctl, uses BTRFS_VOL_NAME_MAX, and >> >> it also looks that this one is more proper. ->> >>=20 +>> >> >> >> Kill BTRFS_PATH_NAME_MAX since no one will use it. ->> >>=20 +>> >> >> > ->> >Nope, BTRFS_PATH_NAME_MAX is specifically used for the ioctl stuff,= - makes the +>> >Nope, BTRFS_PATH_NAME_MAX is specifically used for the ioctl stuff, makes the >> >arguments 4k aligned, this patch is incorrect. Thanks, ->>=20 +>> >> Ok, then what is BTRFS_VOL_NAME_MAX? :) > ->Right now it is only used in the progs. The disk format doesn't reall= -y ->have a max there, it is just to keep names usable. But, we should add= - a +>Right now it is only used in the progs. The disk format doesn't really +>have a max there, it is just to keep names usable. But, we should add a >check in the kernel ioctl side, are you interested in sending a patch >for it? > @@ -27,11 +24,5 @@ Yup, I will do. Thanks. ---=20 +-- "Against stupidity, the gods themselves, contend in vain." - --- -To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = -in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 7a1020a..3e267eb 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -13,26 +13,23 @@ "\00:1\0" "b\0" "On Wed, Jan 21, 2009 at 10:04:08AM -0500, Chris Mason wrote:\n" - ">On Mon, 2009-01-19 at 21:12 +0800, Am=C3=A9rico Wang wrote:\n" + ">On Mon, 2009-01-19 at 21:12 +0800, Am\303\251rico Wang wrote:\n" ">> On Mon, Jan 19, 2009 at 08:03:37AM -0500, Josef Bacik wrote:\n" - ">> >On Mon, Jan 19, 2009 at 08:57:32PM +0800, Am=C3=A9rico Wang wrote:\n" - ">> >>=20\n" + ">> >On Mon, Jan 19, 2009 at 08:57:32PM +0800, Am\303\251rico Wang wrote:\n" + ">> >> \n" ">> >> I found userspace tool, btrfsctl, uses BTRFS_VOL_NAME_MAX, and\n" ">> >> it also looks that this one is more proper.\n" - ">> >>=20\n" + ">> >> \n" ">> >> Kill BTRFS_PATH_NAME_MAX since no one will use it.\n" - ">> >>=20\n" + ">> >> \n" ">> >\n" - ">> >Nope, BTRFS_PATH_NAME_MAX is specifically used for the ioctl stuff,=\n" - " makes the\n" + ">> >Nope, BTRFS_PATH_NAME_MAX is specifically used for the ioctl stuff, makes the\n" ">> >arguments 4k aligned, this patch is incorrect. Thanks,\n" - ">>=20\n" + ">> \n" ">> Ok, then what is BTRFS_VOL_NAME_MAX? :)\n" ">\n" - ">Right now it is only used in the progs. The disk format doesn't reall=\n" - "y\n" - ">have a max there, it is just to keep names usable. But, we should add=\n" - " a\n" + ">Right now it is only used in the progs. The disk format doesn't really\n" + ">have a max there, it is just to keep names usable. But, we should add a\n" ">check in the kernel ioctl side, are you interested in sending a patch\n" ">for it?\n" ">\n" @@ -41,13 +38,7 @@ "\n" "Thanks.\n" "\n" - "--=20\n" - "\"Against stupidity, the gods themselves, contend in vain.\"\n" - "\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-btrfs\" =\n" - "in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + "-- \n" + "\"Against stupidity, the gods themselves, contend in vain.\"" -f728717c4e9faa7d8d8e036d4d61687a1c852c86ed5f6293d53fda7367fe4de3 +85e97b1af933694c399203624e755b3c6cb48de9c6fd88add09c024cf31a4f6f
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.