Re: [Toybox] [PATCH] chown/chgrp with unknown numeric ids

2016-08-20 Thread darken
> > I was grinding through my todo list last night and fixed this, and only > just noticed replying to your message that you'd attached a patch. > (Oops. Sorry.) :-|, well at least it's fixed. The fixes look fairly similar. I need to update tests/chown.test and > tests/chgrp.test to actually

Re: [Toybox] [PATCH] chown/chgrp with unknown numeric ids

2016-08-20 Thread Rob Landley
On 08/20/2016 06:01 AM, darken wrote: > I was grinding through my todo list last night and fixed this, and only > just noticed replying to your message that you'd attached a patch. > (Oops. Sorry.) > > > :-|, well at least it's fixed. > > The fixes look fairly similar. I need to

Re: [Toybox] [PATCH] chown/chgrp with unknown numeric ids

2016-08-20 Thread darken
> If it really bothers you, I can change it back. It just makes the rangetest... sort of inconclusive. Nah doesn't bother me at all. I was just curious and looking to learn about some of these C/linux intricacies. Thanks for the details! 2016-08-20 22:46 GMT+02:00 Rob Landley :

[Toybox] getfattr is insane

2016-08-20 Thread Rob Landley
So setfattr doesn't accept key=value pairs, but instead -n key with optional -v value. Meaning you can only set one per invocation, because... [jazzhands] But getfattr is worse, it's like somebody read The Unix Philosophy by Mike Gancarz, got to the bit about output being scriptable by default,

Re: [Toybox] getfattr is insane

2016-08-20 Thread enh
On Sat, Aug 20, 2016 at 6:52 PM, Rob Landley wrote: > So setfattr doesn't accept key=value pairs, but instead -n key with > optional -v value. Meaning you can only set one per invocation, > because... [jazzhands] > > But getfattr is worse, it's like somebody read The Unix