From: Dinesh Polathula <dpdineshp2@gmail•com>
To: git@vger•kernel.org
Cc: Dinesh <dpdineshp2@gmail•com>
Subject: [PATCH] Allow "-" as a short-hand for "@{-1}" in "git branch -d @{-1}"
Date: Sun, 6 Mar 2016 18:18:14 +0530 [thread overview]
Message-ID: <1457268494-8394-2-git-send-email-dpdineshp2@gmail.com> (raw)
In-Reply-To: <1457268494-8394-1-git-send-email-dpdineshp2@gmail.com>
From: Dinesh <dpdineshp2@gmail•com>
The "-" shorthand can be used as a replacement for "@{-1}" to refer
to the previous branch the user was on in the "git branch -d @{-1}"
command.
Replace "-" argument with "@{-1}" when the command line arguments
are parsed.
Signed-off-by: Dinesh Polathula<dpdineshp2@gmail•com>
---
builtin/branch.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/builtin/branch.c b/builtin/branch.c
index 7b45b6b..98d2c4b 100644
--- a/builtin/branch.c
+++ b/builtin/branch.c
@@ -24,7 +24,7 @@
static const char * const builtin_branch_usage[] = {
N_("git branch [<options>] [-r | -a] [--merged | --no-merged]"),
N_("git branch [<options>] [-l] [-f] <branch-name> [<start-point>]"),
- N_("git branch [<options>] [-r] (-d | -D) <branch-name>..."),
+ N_("git branch [<options>] [-r] (-d | -D) [-] <branch-name>..."),
N_("git branch [<options>] (-m | -M) [<old-branch>] <new-branch>"),
N_("git branch [<options>] [-r | -a] [--points-at]"),
NULL
@@ -658,8 +658,13 @@ int cmd_branch(int argc, const char **argv, const char *prefix)
filter.abbrev = -1;
if (argc == 2 && !strcmp(argv[1], "-h"))
- usage_with_options(builtin_branch_usage, options);
-
+ {
+ usage_with_options(builtin_branch_usage, options);
+ }
+ if (argc == 3 && !strcmp(argv[2], "-"))
+ {
+ argv[2] = "@{-1}";
+ }
git_config(git_branch_config, NULL);
track = git_branch_track;
--
2.8.0.rc0
next prev parent reply other threads:[~2016-03-06 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 12:48 [PATCH] Allow "-" as a short-hand for "@{-1}" in "git branch -d @{-1}" Dinesh Polathula
2016-03-06 12:48 ` Dinesh Polathula [this message]
2016-03-06 19:35 ` Eric Sunshine
2016-03-06 21:09 ` Junio C Hamano
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=1457268494-8394-2-git-send-email-dpdineshp2@gmail.com \
--to=dpdineshp2@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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