From: Jonh Wendell <jonh.wendell@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Jonh Wendell <jonh.wendell@gmail.com>
Subject: [PATCH 1/2] describe: support the syntax "--abbrev=+"
Date: Fri, 12 Sep 2014 11:26:43 -0300 [thread overview]
Message-ID: <1410532004-22769-2-git-send-email-jonh.wendell@gmail.com> (raw)
In-Reply-To: <1410532004-22769-1-git-send-email-jonh.wendell@gmail.com>
It will print just a "+" sign appended to the found tag, if there
are commits between the tag and the supplied commit.
It's useful when you just need a simple output to know if the
supplied commit is an exact match or not.
Signed-off-by: Jonh Wendell <jonh.wendell@gmail.com>
---
builtin/describe.c | 26 +++++++++++++++++++++-----
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/builtin/describe.c b/builtin/describe.c
index ee6a3b9..3a5c052 100644
--- a/builtin/describe.c
+++ b/builtin/describe.c
@@ -30,6 +30,7 @@ static int have_util;
static const char *pattern;
static int always;
static const char *dirty;
+static int simple_abbrev = 0;
/* diff-index command arguments to check if working tree is dirty. */
static const char *diff_index_args[] = {
@@ -378,8 +379,12 @@ static void describe(const char *arg, int last_one)
}
display_name(all_matches[0].name);
- if (abbrev)
- show_suffix(all_matches[0].depth, cmit->object.sha1);
+ if (abbrev) {
+ if (simple_abbrev)
+ printf("+");
+ else
+ show_suffix(all_matches[0].depth, cmit->object.sha1);
+ }
if (dirty)
printf("%s", dirty);
printf("\n");
@@ -388,6 +393,16 @@ static void describe(const char *arg, int last_one)
clear_commit_marks(cmit, -1);
}
+static int parse_opt_abbrev_for_describe_cb(const struct option *opt, const char *arg, int unset)
+{
+ if (arg && !strncmp(arg, "+", 1)) {
+ simple_abbrev = 1;
+ return 0;
+ }
+
+ return parse_opt_abbrev_cb(opt, arg, unset);
+}
+
int cmd_describe(int argc, const char **argv, const char *prefix)
{
int contains = 0;
@@ -398,7 +413,6 @@ int cmd_describe(int argc, const char **argv, const char *prefix)
OPT_BOOL(0, "tags", &tags, N_("use any tag, even unannotated")),
OPT_BOOL(0, "long", &longformat, N_("always use long format")),
OPT_BOOL(0, "first-parent", &first_parent, N_("only follow first parent")),
- OPT__ABBREV(&abbrev),
OPT_SET_INT(0, "exact-match", &max_candidates,
N_("only output exact matches"), 0),
OPT_INTEGER(0, "candidates", &max_candidates,
@@ -410,6 +424,8 @@ int cmd_describe(int argc, const char **argv, const char *prefix)
{OPTION_STRING, 0, "dirty", &dirty, N_("mark"),
N_("append <mark> on dirty working tree (default: \"-dirty\")"),
PARSE_OPT_OPTARG, NULL, (intptr_t) "-dirty"},
+ {OPTION_CALLBACK, 0, "abbrev", &abbrev, N_("n"), N_("use <n> digits to display SHA-1s"),
+ PARSE_OPT_OPTARG, &parse_opt_abbrev_for_describe_cb, 0},
OPT_END(),
};
@@ -425,8 +441,8 @@ int cmd_describe(int argc, const char **argv, const char *prefix)
save_commit_buffer = 0;
- if (longformat && abbrev == 0)
- die(_("--long is incompatible with --abbrev=0"));
+ if (longformat && (abbrev == 0 || simple_abbrev))
+ die(_("--long is incompatible with --abbrev=+ or --abbrev=0"));
if (contains) {
struct argv_array args;
--
1.9.3
next prev parent reply other threads:[~2014-09-12 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 14:26 [PATCH 0/2] describe: support the syntax "--abbrev=+" Jonh Wendell
2014-09-12 14:26 ` Jonh Wendell [this message]
2014-09-14 8:18 ` [PATCH 1/2] " Jeff King
2014-09-14 8:56 ` Eric Sunshine
2014-09-12 14:26 ` [PATCH 2/2] describe: Add documentation for "--abbrev=+" Jonh Wendell
2014-09-14 8:23 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2014-08-23 17:13 [PATCH 0/2] describe: support the syntax "--abbrev=+" Jonh Wendell
2014-08-23 17:13 ` [PATCH 1/2] " Jonh Wendell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1410532004-22769-2-git-send-email-jonh.wendell@gmail.com \
--to=jonh.wendell@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).