# [PATCH] tag: fix some mis-organized options in "-h" listing

2 messages from 2015-03-12 to 2015-03-12. Participants: Jeff King, Junio C Hamano.
Thread: https://gitlist.dev/t/38786

## Jeff King, 2015-03-12 18:15

Subject: [PATCH] tag: fix some mis-organized options in "-h" listing
Message-ID: <20150312181509.GA20987@peff.net>
URL: https://gitlist.dev/e/20150312181509.GA20987%40peff.net

```
Running "git tag -h" currently prints:

  [...]
  Tag creation options
      [...]
      --column[=<style>]    show tag list in columns
      --sort <type>         sort tags

  Tag listing options
      --contains <commit>   print only tags that contain the commit
      --points-at <object>  print only tags of the object

The "--column" and "--sort" options should go under the "Tag listing" group.

Signed-off-by: Jeff King <peff@peff.net>
---
 builtin/tag.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/builtin/tag.c b/builtin/tag.c
index 4194b9a..6f07ac6 100644
--- a/builtin/tag.c
+++ b/builtin/tag.c
@@ -605,13 +605,13 @@ int cmd_tag(int argc, const char **argv, const char *prefix)
 		OPT_STRING('u', "local-user", &keyid, N_("key-id"),
 					N_("use another key to sign the tag")),
 		OPT__FORCE(&force, N_("replace the tag if exists")),
+
+		OPT_GROUP(N_("Tag listing options")),
 		OPT_COLUMN(0, "column", &colopts, N_("show tag list in columns")),
 		{
 			OPTION_CALLBACK, 0, "sort", &tag_sort, N_("type"), N_("sort tags"),
 			PARSE_OPT_NONEG, parse_opt_sort
 		},
-
-		OPT_GROUP(N_("Tag listing options")),
 		{
 			OPTION_CALLBACK, 0, "contains", &with_commit, N_("commit"),
 			N_("print only tags that contain the commit"),
-- 
2.3.2.472.geadab3c

```

## Junio C Hamano, 2015-03-12 19:10

Subject: Re: [PATCH] tag: fix some mis-organized options in "-h" listing
Message-ID: <xmqq61a62frl.fsf@gitster.dls.corp.google.com>
URL: https://gitlist.dev/e/xmqq61a62frl.fsf%40gitster.dls.corp.google.com
In-Reply-To: <20150312181509.GA20987@peff.net>

```
Thanks.

Even though this dates back to d96e3c15 (tag: add --column,
2012-04-13), I do not think it is worth backporting it to v1.7.x
series, so I'll queue the fix for a bit newer maintenance track,
perhaps for v2.1.x and above.

```