From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: [PATCH 0/2] Fix invalid revision error messages for 1.8.3
Date: Tue, 21 May 2013 16:11:53 +0530 [thread overview]
Message-ID: <1369132915-25657-1-git-send-email-artagnon@gmail.com> (raw)
Hi,
Seeing other patches on the list, I decided that I should do something
for 1.8.3 as well (as opposed to constantly writing new features). So
here's my contribution.
The first error message has annoyed me endlessly, and I took this
opportunity to fix it. Interested people can sprinkle in some advice
later. The second one is a low-hanging "while we're there".
Thanks.
Ramkumar Ramachandra (2):
sha1_name: fix error message for @{u}
sha1_name: fix error message for @{<N>}, @{<date>}
sha1_name.c | 17 +++++++++++------
t/t1507-rev-parse-upstream.sh | 15 +++++----------
2 files changed, 16 insertions(+), 16 deletions(-)
--
1.8.3.rc3.6.ga9126d5.dirty
next reply other threads:[~2013-05-21 10:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 10:41 Ramkumar Ramachandra [this message]
2013-05-21 10:41 ` [PATCH 1/2] sha1_name: fix error message for @{u} Ramkumar Ramachandra
2013-05-21 16:42 ` Junio C Hamano
2013-05-21 17:56 ` Ramkumar Ramachandra
2013-05-21 18:02 ` Junio C Hamano
2013-05-21 18:04 ` Ramkumar Ramachandra
2013-05-21 18:09 ` Junio C Hamano
2013-05-21 19:19 ` Ramkumar Ramachandra
2013-05-21 20:08 ` Junio C Hamano
2013-05-21 20:14 ` Ramkumar Ramachandra
2013-05-21 20:33 ` Junio C Hamano
2013-05-21 10:41 ` [PATCH 2/2] sha1_name: fix error message for @{<N>}, @{<date>} Ramkumar Ramachandra
2013-05-21 16:52 ` Junio C Hamano
2013-05-21 17:38 ` Kevin Bracey
2013-05-21 18:09 ` Ramkumar Ramachandra
2013-05-21 16:36 ` [PATCH 0/2] Fix invalid revision error messages for 1.8.3 Junio C Hamano
2013-05-21 17:50 ` Ramkumar Ramachandra
2013-05-21 17:57 ` Junio C Hamano
2013-05-21 18:16 ` Ramkumar Ramachandra
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=1369132915-25657-1-git-send-email-artagnon@gmail.com \
--to=artagnon@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).