From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/2] cosmetic improvements for "git show tag"
Date: Fri, 17 Jul 2009 19:16:22 -0400 [thread overview]
Message-ID: <20090717231622.GA13511@coredump.intra.peff.net> (raw)
Right now, if you do:
$ git tag -m 'annotated tag message' foo
$ git show foo
you get:
tag foo
Tagger: Jeff King <peff@peff.net>
Date: Fri Jul 17 19:10:54 2009 -0400
annotated tag message
commit 88c17f18d7f3091508218b36a17cdf0dfd56ae65
Author: Jeff King <peff@peff.net>
Date: Fri Jul 17 19:10:50 2009 -0400
commit message
diff ...
which is IMHO quite hard to read. These two one-liner patches improve
the output to:
tag foo
Tagger: Jeff King <peff@peff.net>
Date: Fri Jul 17 19:10:54 2009 -0400
annotated tag message
commit 88c17f18d7f3091508218b36a17cdf0dfd56ae65
Author: Jeff King <peff@peff.net>
Date: Fri Jul 17 19:10:50 2009 -0400
commit message
diff ...
which I find much more readable. The changes are localized to "git
show", and since it is porcelain, I don't think there should be any
negative fallout by changing the output.
---
Jeff King (2):
show: suppress extra newline when showing annotated tag
show: add space between tag body and tagged object
builtin-log.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
next reply other threads:[~2009-07-17 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 23:16 Jeff King [this message]
2009-07-17 23:18 ` [PATCH 1/2] show: suppress extra newline when showing annotated tag Jeff King
2009-07-18 3:25 ` [PATCH 1/2] " Nicolas Sebrecht
2009-07-18 3:47 ` Jeff King
2009-07-17 23:22 ` [PATCH 2/2] show: add space between tag body and tagged object Jeff King
2009-07-18 1:10 ` [PATCH 0/2] Re: cosmetic improvements for "git show tag" Nicolas Sebrecht
2009-07-18 1:47 ` Jeff King
2009-07-18 10:14 ` Jeff King
2009-07-19 18:05 ` 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=20090717231622.GA13511@coredump.intra.peff.net \
--to=peff@peff.net \
--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).