Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+xfsprogs\:\s+xfs_quota\s+allow\s+user\s+or\s+group\s+names\s+beginning\s+with\s+digits\s*$/: 3 ]

Total 3 documents matching your query.

1. [PATCH] xfsprogs: xfs_quota allow user or group names beginning with digits (score: 1)
Author: rjohnston@xxxxxxx
Date: Wed, 17 Apr 2013 13:32:53 -0500
xfs_quota does not properly parse users or groups that begin with a number. Only call atoi when user or group consists of digits only. Signed-off-by: Rich Johnston <rjohnston@xxxxxxx> -- include/inpu
/archives/xfs/2013-04/msg00407.html (8,762 bytes)

2. Re: [PATCH] xfsprogs: xfs_quota allow user or group names beginning with digits (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Sun, 21 Apr 2013 00:55:09 -0500
<some kind of email that doesn't show up when I hit reply so repasting ;)> Seems sane to me. I'd change i=0 to i = 0, but *shrug* [xfsprogs]$ grep -r "i = 0" * | wc -l 404 [xfsprogs]$ grep -r "i=0" *
/archives/xfs/2013-04/msg00459.html (11,589 bytes)

3. Re: [PATCH] xfsprogs: xfs_quota allow user or group names beginning with digits (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Mon, 22 Apr 2013 12:45:01 +1000
bool is the correct type, not boolean_t. My CRC patchset makes userspace fall in line with the removal of boolean_t from the kernel code, so we should probably make this correct from the start. ;) Ch
/archives/xfs/2013-04/msg00469.html (8,748 bytes)


This search system is powered by Namazu