5 Commits (f38e952f4eb3a5f4996a2a41bd0eedc98b6637de)

Author	SHA1	Message	Date
Cao Shufeng	995c5a07ea	fix kubectl -o ... Fix kubectl -o error message: Before this change: ```shell kubectl get pods -o foo error: unable to match a printer suitable for the output format "" and the options specified: &get.PrintFlags{JSONYamlPrintFlags:(*genericclioptions.JSONYamlPrintFlags)(0x23aa610), NamePrintFlags:(*genericclioptions.NamePrintFlags)(0xc42058b4e0), TemplateFlags:(*printers.KubeTemplatePrintFlags)(0xc4206765e0), CustomColumnsFlags:(*printers.CustomColumnsPrintFlags)(0xc420676620), HumanReadableFlags:(*get.HumanPrintFlags)(0xc4204eb180), NoHeaders:(*bool)(0xc4206fefbc), OutputFormat:(*string)(0xc42058b4d0)} ``` After this change: ```shell Kubectl get pods -o foo error: unable to match a printer suitable for the output format "aaa", allowed formats are: custom-columns,custom-columns-file,go-template,go-template-file,json,jsonpath,jsonpath-file,name,template,templatefile,wide,yaml ```	2018-06-05 19:49:07 +08:00
juanvallejo	d1603c9560	move PrintOptions to genericclioptions	2018-05-21 14:59:41 -04:00
juanvallejo	ac6ca38dd7	report outputFormat in PrintFlags err	2018-04-25 16:35:56 -04:00
juanvallejo	8a7b2fdda3	begin wiring printopts through complete commands	2018-04-13 11:50:54 -04:00
juanvallejo	ec672ca279	wire through template PrintFlags	2018-03-27 18:11:01 -04:00