diff for duplicates of <20131212232443.GL31386@dastard> diff --git a/a/1.txt b/N1/1.txt index a880e4b..44301da 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -69,3 +69,8 @@ Dave. -- Dave Chinner david@fromorbit.com + +_______________________________________________ +xfs mailing list +xfs@oss.sgi.com +http://oss.sgi.com/mailman/listinfo/xfs diff --git a/a/content_digest b/N1/content_digest index bda224f..de82b37 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,16 +4,16 @@ "Subject\0Re: [PATCH 2/4 v3] fiemap: add EXTENT_DATA_COMPRESSED flag\0" "Date\0Fri, 13 Dec 2013 10:24:43 +1100\0" "To\0David Sterba <dsterba@suse.cz>\0" - "Cc\0linux-fsdevel@vger.kernel.org" - adilger@dilger.ca + "Cc\0adilger@dilger.ca" linux-nilfs@vger.kernel.org mfasheh@suse.com xfs@oss.sgi.com hch@infradead.org - linux-btrfs@vger.kernel.org + ocfs2-devel@oss.oracle.com viro@zeniv.linux.org.uk + linux-fsdevel@vger.kernel.org linux-ext4@vger.kernel.org - " ocfs2-devel@oss.oracle.com\0" + " linux-btrfs@vger.kernel.org\0" "\00:1\0" "b\0" "On Thu, Dec 12, 2013 at 04:25:59PM +0100, David Sterba wrote:\n" @@ -86,6 +86,11 @@ "Dave.\n" "-- \n" "Dave Chinner\n" - david@fromorbit.com + "david@fromorbit.com\n" + "\n" + "_______________________________________________\n" + "xfs mailing list\n" + "xfs@oss.sgi.com\n" + http://oss.sgi.com/mailman/listinfo/xfs -44b932198683dfb1b4181e8156cf32fc921a5d1f234c17f4db559f847804560c +48b4085eb26f688963ed509b746cf13f1662812c176d2329ce62bafc7eb33fcc
diff --git a/a/1.txt b/N2/1.txt index a880e4b..8fe6a1f 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -16,7 +16,7 @@ by the API. Yes, the implementation zeros them, but there's nothing in the documentation that says "reserved fields must be zero". Hence I think we should just set it for every extent. ->From the point of view of the kernel API (fiemap_fill_next_extent), +From the point of view of the kernel API (fiemap_fill_next_extent), passing the physical extent size in the "len" parameter for normal extents, then passing 0 for the "physical length" makes absolutely no sense. @@ -69,3 +69,8 @@ Dave. -- Dave Chinner david@fromorbit.com + +_______________________________________________ +xfs mailing list +xfs@oss.sgi.com +http://oss.sgi.com/mailman/listinfo/xfs diff --git a/a/content_digest b/N2/content_digest index bda224f..cfd8d46 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -4,16 +4,16 @@ "Subject\0Re: [PATCH 2/4 v3] fiemap: add EXTENT_DATA_COMPRESSED flag\0" "Date\0Fri, 13 Dec 2013 10:24:43 +1100\0" "To\0David Sterba <dsterba@suse.cz>\0" - "Cc\0linux-fsdevel@vger.kernel.org" - adilger@dilger.ca + "Cc\0adilger@dilger.ca" linux-nilfs@vger.kernel.org mfasheh@suse.com xfs@oss.sgi.com hch@infradead.org - linux-btrfs@vger.kernel.org + ocfs2-devel@oss.oracle.com viro@zeniv.linux.org.uk + linux-fsdevel@vger.kernel.org linux-ext4@vger.kernel.org - " ocfs2-devel@oss.oracle.com\0" + " linux-btrfs@vger.kernel.org\0" "\00:1\0" "b\0" "On Thu, Dec 12, 2013 at 04:25:59PM +0100, David Sterba wrote:\n" @@ -34,7 +34,7 @@ "in the documentation that says \"reserved fields must be zero\".\n" "Hence I think we should just set it for every extent.\n" "\n" - ">From the point of view of the kernel API (fiemap_fill_next_extent),\n" + "From the point of view of the kernel API (fiemap_fill_next_extent),\n" "passing the physical extent size in the \"len\" parameter for normal\n" "extents, then passing 0 for the \"physical length\" makes absolutely\n" "no sense.\n" @@ -86,6 +86,11 @@ "Dave.\n" "-- \n" "Dave Chinner\n" - david@fromorbit.com + "david@fromorbit.com\n" + "\n" + "_______________________________________________\n" + "xfs mailing list\n" + "xfs@oss.sgi.com\n" + http://oss.sgi.com/mailman/listinfo/xfs -44b932198683dfb1b4181e8156cf32fc921a5d1f234c17f4db559f847804560c +fea003030a6ccffda44b4fcc208884444111a7495c8de31eaf45b6bcab50fa9e
diff --git a/a/1.txt b/N3/1.txt index a880e4b..1908b1d 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -16,7 +16,7 @@ by the API. Yes, the implementation zeros them, but there's nothing in the documentation that says "reserved fields must be zero". Hence I think we should just set it for every extent. ->From the point of view of the kernel API (fiemap_fill_next_extent), +From the point of view of the kernel API (fiemap_fill_next_extent), passing the physical extent size in the "len" parameter for normal extents, then passing 0 for the "physical length" makes absolutely no sense. @@ -68,4 +68,4 @@ Cheers, Dave. -- Dave Chinner -david@fromorbit.com +david at fromorbit.com diff --git a/a/content_digest b/N3/content_digest index bda224f..09543c9 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -1,8 +1,8 @@ "ref\0cover.1386778302.git.dsterba@suse.cz\0" "ref\04f8d5dc5b51a43efaf16c39398c23a6276e40a30.1386778303.git.dsterba@suse.cz\0" "From\0Dave Chinner <david@fromorbit.com>\0" - "Subject\0Re: [PATCH 2/4 v3] fiemap: add EXTENT_DATA_COMPRESSED flag\0" - "Date\0Fri, 13 Dec 2013 10:24:43 +1100\0" + "Subject\0[Ocfs2-devel] [PATCH 2/4 v3] fiemap: add EXTENT_DATA_COMPRESSED flag\0" + "Date\0Thu, 12 Dec 2013 23:25:13 -0000\0" "To\0David Sterba <dsterba@suse.cz>\0" "Cc\0linux-fsdevel@vger.kernel.org" adilger@dilger.ca @@ -34,7 +34,7 @@ "in the documentation that says \"reserved fields must be zero\".\n" "Hence I think we should just set it for every extent.\n" "\n" - ">From the point of view of the kernel API (fiemap_fill_next_extent),\n" + "From the point of view of the kernel API (fiemap_fill_next_extent),\n" "passing the physical extent size in the \"len\" parameter for normal\n" "extents, then passing 0 for the \"physical length\" makes absolutely\n" "no sense.\n" @@ -86,6 +86,6 @@ "Dave.\n" "-- \n" "Dave Chinner\n" - david@fromorbit.com + david at fromorbit.com -44b932198683dfb1b4181e8156cf32fc921a5d1f234c17f4db559f847804560c +9c2b41c8113e6d25fe8853a7e1a45c4bc11d8389af02ce04121075113c226df4
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.