From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Conrad Irwin" <conrad.irwin@gmail.com>,
"Sitaram Chamarty" <sitaramc@gmail.com>,
"Michael J Gruber" <git@drmicha.warpmail.net>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
"Jeff King" <peff@peff.net>,
"Brian M . Carlson" <sandals@crustytoothpaste.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH v2 0/3] rev-parse case insensitivity & @{p} synonym
Date: Sun, 26 Mar 2017 12:16:51 +0000 [thread overview]
Message-ID: <20170326121654.22035-1-avarab@gmail.com> (raw)
In-Reply-To: <xmqq1stszxn4.fsf@gitster.mtv.corp.google.com>
This v2 addresses the feedback on my "rev-parse: match @{u}, @{push}
and ^{<type>} case-insensitively" patch. I've split this into a 3
patch series:
Ævar Arnfjörð Bjarmason (3):
rev-parse: match @{upstream}, @{u} and @{push} case-insensitively
Reworded the documentation as Junio suggested in
<xmqq1stszxn4.fsf@gitster.mtv.corp.google.com>.
rev-parse: add @{p} as a synonym for @{push}
While I'm at it why don't we have a shorthand for @{push} like
@{upstream}? Add it as @{p}.
rev-parse: match ^{<type>} case-insensitively
Junio didn't want ^{<type>} case-insensitive "for now", so I split it
out of the first patch.
I'm not overly excited about it, neither is Junio, so this'll probably
be dropped, but I wanted to submit it as a standalone patch in case
anyone wanted to pick this up in the future.
Documentation/revisions.txt | 15 ++++++++++++---
git-compat-util.h | 1 +
sha1_name.c | 14 +++++++-------
strbuf.c | 9 +++++++++
t/t1450-fsck.sh | 7 +++++++
t/t1507-rev-parse-upstream.sh | 15 +++++++++++----
t/t1511-rev-parse-caret.sh | 13 +++++++++++++
t/t1514-rev-parse-push.sh | 10 ++++++++--
8 files changed, 68 insertions(+), 16 deletions(-)
--
2.11.0
next prev parent reply other threads:[~2017-03-26 12:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 22:34 [PATCH] rev-parse: match @{u}, @{push} and ^{<type>} case-insensitively Ævar Arnfjörð Bjarmason
2017-03-19 9:19 ` Duy Nguyen
2017-03-19 10:04 ` Ævar Arnfjörð Bjarmason
2017-03-19 12:55 ` Junio C Hamano
2017-03-19 14:26 ` Ævar Arnfjörð Bjarmason
2017-03-19 22:53 ` Junio C Hamano
2017-03-26 12:16 ` Ævar Arnfjörð Bjarmason [this message]
2017-03-26 12:16 ` [PATCH v2 1/3] rev-parse: match @{upstream}, @{u} and @{push} case-insensitively Ævar Arnfjörð Bjarmason
2017-03-27 0:27 ` Junio C Hamano
2017-03-27 11:16 ` [PATCH v3] " Ævar Arnfjörð Bjarmason
2017-03-27 17:45 ` Junio C Hamano
2017-03-27 18:05 ` Ævar Arnfjörð Bjarmason
2017-03-26 12:16 ` [PATCH v2 2/3] rev-parse: add @{p} as a synonym for @{push} Ævar Arnfjörð Bjarmason
2017-03-27 2:53 ` Jeff King
2017-03-27 7:52 ` Ævar Arnfjörð Bjarmason
2017-03-26 12:16 ` [PATCH v2 3/3] rev-parse: match ^{<type>} case-insensitively Ævar Arnfjörð Bjarmason
2017-03-27 0:36 ` Junio C Hamano
2017-03-27 2:58 ` Jeff King
2017-03-27 5:39 ` Junio C Hamano
2017-03-27 7:11 ` Jeff King
2017-03-27 7:33 ` Ævar Arnfjörð Bjarmason
2017-03-21 19:19 ` [PATCH] rev-parse: match @{u}, @{push} and " Ævar Arnfjörð Bjarmason
2017-03-21 19:26 ` Junio C Hamano
2017-03-21 19:43 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170326121654.22035-1-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=conrad.irwin@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=sitaramc@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).