From: Kenny Lee Sin Cheong <kenny.lee28@gmail.com>
To: git@vger.kernel.org
Cc: Kenny Lee Sin Cheong <kenny.lee28@gmail.com>
Subject: [PATCH/RFC 0/2][GSoC] revision.c: Allow "-" as stand-in for "@{-1}" everywhere a branch is allowed
Date: Mon, 16 Mar 2015 11:11:41 -0400 [thread overview]
Message-ID: <1426518703-15785-1-git-send-email-kenny.lee28@gmail.com> (raw)
This is an attempt at a microproject for GSoC
An attempt to add revision range support to Junio's JFF patch sent a few days ago. The first patch is the a copy of the one he posted.
I was wondering if it was a good idea to add support for commands like "<rev>..-". Files that starts with "-" requires "--" or a "./" format but what if we have a file named "next..-" and call "git log next..-" ?
Junio C Hamano (1):
"-" and "@{-1}" on various programs
Kenny Lee Sin Cheong (1):
Add revision range support on "-" and "@{-1}"
builtin/checkout.c | 3 ---
builtin/merge.c | 3 +--
builtin/revert.c | 2 --
revision.c | 16 +++++++++++++--
sha1_name.c | 57 +++++++++++++++++++++++++++++++++---------------------
5 files changed, 50 insertions(+), 31 deletions(-)
--
2.3.2.225.gebdc58a
next reply other threads:[~2015-03-16 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:11 Kenny Lee Sin Cheong [this message]
2015-03-16 15:11 ` [PATCH 1/2] "-" and "@{-1}" on various programs Kenny Lee Sin Cheong
2015-03-16 15:11 ` [PATCH 2/2] Add revision range support on "-" and "@{-1}" Kenny Lee Sin Cheong
2015-03-16 18:22 ` Junio C Hamano
2015-03-17 6:49 ` Junio C Hamano
2015-03-17 21:25 ` Kenny Lee Sin Cheong
2015-03-17 22:16 ` Junio C Hamano
2015-03-24 0:09 ` Kenny Lee Sin Cheong
2015-03-25 22:24 ` 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=1426518703-15785-1-git-send-email-kenny.lee28@gmail.com \
--to=kenny.lee28@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).