On Nov 19, 2014, at 10:33 AM, Matthew Ahrens <mahr...@delphix.com> wrote:
>
>
> On Wed, Nov 19, 2014 at 10:08 AM, Joshua M. Clulow <j...@sysmgr.org> wrote:
> On 18 November 2014 13:55, Matthew Ahrens <mahr...@delphix.com> wrote:
> >> This seems a reasonable structure to me, except that I would make the
> >> keys precisely the same string (case included) as what would be
> >> specified in the "-o" arguments, rather than using the value that
> >> would display in the headings for human readable output.
> > And rather than using the standard property name (e.g. "referenced")? This
> > seems less standardized to me, but I guess parroting back the way they
> > specified it (e.g. "RefeR") should be workable as well.
>
> Sorry, I meant to convey that it should be both spelt the same, and in
> the same (i.e. lower) case, as it is in the input to the "-o" option.
> I was reasonably sure that the "-o" option did not accept mixed- or
> title-case strings and do "the right thing" with them.
>
>
> Ah, right, sorry about that. So it's just giving them back the column header
> vs the standard name. i.e. if I do "zfs list -J -o refer" then the output
> will call the property "refer", and if I do "zfs list -J -o referenced", then
> the output will call the property "referenced".
>
> In my opinion, for programmatic use (e.g. -J), the standard (full) property
> name should always be used ("referenced", not "refer"), and the output should
> always be in parseable format ("12345", not "12.0K").
agree
-- richard
>
> --matt
>
> _______________________________________________
> developer mailing list
> developer@open-zfs.org
> http://lists.open-zfs.org/mailman/listinfo/developer
_______________________________________________
developer mailing list
developer@open-zfs.org
http://lists.open-zfs.org/mailman/listinfo/developer
