From: Elena Petrashen <elena.petrashen@gmail.com>
To: git@vger.kernel.org
Cc: Elena Petrashen <elena.petrashen@gmail.com>
Subject: [PATCH][Outreachy] branch: allow - as abbreviation of '@{-1}'
Date: Fri, 18 Mar 2016 15:47:11 +0300 [thread overview]
Message-ID: <1458305231-2333-1-git-send-email-elena.petrashen@gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 1170 bytes --]
Signed-off-by: Elena Petrashen <elena.petrashen@gmail.com>
---
Hi everyone,
As my first Outreachy submission micropoject I’ve chosen to try to approach “Allow “-“ as a short-hand for “@{-1}” in more places.” (http://git.github.io/SoC-2016-Microprojects/ (Cf. $gmane/230828))
My goal was to teach git branch to accept - shortcut and interpret it as “previous working branch”, i.e $git branch -D -
Really looking forward to hear what do you think, so please let me know if something is done incorrectly, etc.
Thank you,
Elena
builtin/branch.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/builtin/branch.c b/builtin/branch.c
index 7b45b6b..9d0f8a7 100644
--- a/builtin/branch.c
+++ b/builtin/branch.c
@@ -675,6 +675,13 @@ int cmd_branch(int argc, const char **argv, const char *prefix)
argc = parse_options(argc, argv, prefix, options, builtin_branch_usage,
0);
+ int i;
+ for (i = 0; i < argc; i++) {
+ if (!strcmp(argv[i], "-")) {
+ argv[i] = "@{-1}";
+ }
+ }
+
if (!delete && !rename && !edit_description && !new_upstream && !unset_upstream && argc == 0)
list = 1;
--
1.9.1
next reply other threads:[~2016-03-18 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 12:47 Elena Petrashen [this message]
2016-03-18 16:10 ` [PATCH][Outreachy] branch: allow - as abbreviation of '@{-1}' Junio C Hamano
2016-03-18 17:02 ` Mike Hommey
2016-03-18 18:15 ` Eric Sunshine
2016-03-18 18:13 ` Eric Sunshine
2016-03-21 15:12 ` elena petrashen
2016-03-21 16:03 ` Eric Sunshine
2016-03-21 16:07 ` 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=1458305231-2333-1-git-send-email-elena.petrashen@gmail.com \
--to=elena.petrashen@gmail.com \
--cc=git@vger.kernel.org \
/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).