On Friday May 9, bfields@xxxxxxxxxxxx wrote: > Um, sorry about that subject line. I liked it ;-) Gave a bit of an informal feel.... > > On Fri, May 09, 2008 at 03:23:19PM -0400, J. Bruce Fields wrote: > > From: J. Bruce Fields <bfields@xxxxxxxxxxxxxx> > > > > Commit f15364bd4cf8799a7677b6daeed7b67d9139d974 ("IPv6 support for NFS > > server export caches") dropped a couple spaces, rendering the output > > here difficult to read. > > > > (However note that we expect the output to be parsed only by humans, not > > machines, so this shouldn't have broken any userland software.) > > > > Signed-off-by: J. Bruce Fields <bfields@xxxxxxxxxxxxxx> > > Cc: Aurelien Charbon <aurelien.charbon@xxxxxxxx> > > Cc: Neil Brown <neilb@xxxxxxx> > > Cc: Brian Haley <brian.haley@xxxxxx> > > Cc: YOSHIFUJI Hideaki / $(O$h掩 <yoshfuji@xxxxxxxxxxxxxx> > > > > --- > > net/sunrpc/svcauth_unix.c | 4 ++-- > > 1 files changed, 2 insertions(+), 2 deletions(-) > > > > I just noticed this while doing some debugging at Connectathon. I'm > > undecided whether to take it seriously. Does anyone other than me use > > these /content files? I suppose it should probably go into 2.6.26 but > > not 2.6.25.x. I don't think any code uses them, but it's very good to be able to look at them when something doesn't seem to be working as expected. But I don't think the patch would apply to 2.6.25. 'git name-rev' on the offending commit say: f15364bd4cf8799a7677b6daeed7b67d9139d974 tags/v2.6.26-rc1~1083^2~47 which means it was in 2.6.26-rc1 but not the previous release. NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html