From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/3] Iron output of describe --contains --all
Date: Sun, 7 Jul 2013 18:13:13 +0530 [thread overview]
Message-ID: <1373200996-9753-1-git-send-email-artagnon@gmail.com> (raw)
Hi,
I actually sent these patches to the list last month, but nobody
seemed to be interested. This is an unedited resend.
I looked into adding tests, but decided that it was a lost cause: the
output is too loosely defined for any scripts to rely on it strongly.
[1/3] already shows a race between branches and tags. For another
example, consider two tags are pointing to same commit (D and R in
t6120-describe.sh). Run the following on the two tags and see what
happens for yourself:
$ git describe --contains
$ git describe --all
$ git describe --tags
Now think about various combinations of these options. I'm not saying
that it's a Bad Thing (TM), but that nobody has bothered tightening
the output.
My main motivation for doing this series is my prompt: I don't want to
see
artagnon|(tags/v1.8.3^0)~/src/git$
when
artagnon|(v1.8.3)~/src/git$
is so much more pleasant and consistent. Obviously, hacking around
this problem in the prompt script is the Wrong thing to do.
Thanks.
Ramkumar Ramachandra (3):
name-rev: fix assumption about --name-only usage
name-rev: strip trailing ^0 in when --name-only
name-rev doc: rewrite --stdin paragraph
Documentation/git-name-rev.txt | 12 +++++++-----
builtin/name-rev.c | 12 +++++++++++-
t/t4202-log.sh | 8 ++++----
t/t6007-rev-list-cherry-pick-file.sh | 32 ++++++++++++++++----------------
4 files changed, 38 insertions(+), 26 deletions(-)
--
1.8.3.2.737.gcbc076a.dirty
next reply other threads:[~2013-07-07 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 12:43 Ramkumar Ramachandra [this message]
2013-07-07 12:43 ` [PATCH 1/3] name-rev: fix assumption about --name-only usage Ramkumar Ramachandra
2013-07-07 18:18 ` Junio C Hamano
2013-07-08 13:18 ` Ramkumar Ramachandra
2013-07-07 12:43 ` [PATCH 2/3] name-rev: strip trailing ^0 in when --name-only Ramkumar Ramachandra
2013-07-07 18:16 ` Junio C Hamano
2013-07-07 22:03 ` Junio C Hamano
2013-07-08 13:00 ` Ramkumar Ramachandra
2013-07-07 12:43 ` [PATCH 3/3] name-rev doc: rewrite --stdin paragraph Ramkumar Ramachandra
2013-07-07 18:04 ` 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
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=1373200996-9753-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.
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).