Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+0\/4\]\s+xfs\s+fixes\s+for\s+Linux\s+3\.2\-rc3\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+0\/4\]\s+xfs\s+fixes\s+for\s+Linux\s+3\.2\-rc3\s*$/: 3 ]

Total 3 documents matching your query.

1. [PATCH 0/4] xfs fixes for Linux 3.2-rc3 (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 28 Nov 2011 03:17:32 -0500; These are the patches that I think should still go into Linux 3.2. The first two are fairly trivial fixes for crashes that can be reproduced by users action or filesystem corruption. The third is a a; /archives/xfs/2011-11/msg00531.html (7,376 bytes)
2. Re: [PATCH 0/4] xfs fixes for Linux 3.2-rc3 (score: 1): Author: Ben Myers <bpm@xxxxxxx>; Date: Tue, 29 Nov 2011 13:23:00 -0600; Yep. This last one is pretty big. Could it wait for 3.3? -Ben; /archives/xfs/2011-11/msg00584.html (8,601 bytes)
3. Re: [PATCH 0/4] xfs fixes for Linux 3.2-rc3 (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 30 Nov 2011 03:54:07 -0500; It's not that big, and if we manage to push it out ASAP it's not even that late in the cycle. Given that people are getting fast hardware managing to hit all kinds of weird AIL and log reservation ha; /archives/xfs/2011-11/msg00590.html (9,091 bytes)

Current List: 1 - 3
Page: [1]