From: Jeff King <peff@peff.net>
To: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 0/2] Re: cosmetic improvements for "git show tag"
Date: Fri, 17 Jul 2009 21:47:43 -0400 [thread overview]
Message-ID: <20090718014743.GA16381@coredump.intra.peff.net> (raw)
In-Reply-To: <20090718011006.GB12968@vidovic>
On Sat, Jul 18, 2009 at 03:10:06AM +0200, Nicolas Sebrecht wrote:
> Nice. What about adding an extra newline between tags?
>
> $ git tag v1.6.1 v1.6.2
>
> <snip>
>
> + link:RelNotes-1.6.1.txt[1.6.1].
> +
> * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
>
> * release notes for
> tag v1.6.2
> Tagger: Junio C Hamano <gitster@pobox.com>
> Date: Tue Mar 3 23:37:25 2009 -0800
>
> <snip>
>
> IOW, between " * release notes for" and "tag v1.6.2" here.
Hmph. I thought that should just work, because of the newline after the
commit. But it seems that you only get that if the next thing is a
commit. Hrm.. and it is even worse. The code to print that newline comes
from printing the second commit, which says "oh, we've already printed a
commit" and adds the newline.
So when you show two tags you get:
tag foo
message
commit foo^{}
message
tag bar
commit bar^{}
That is, the newline is actually stuck in the wrong place. So we
actually need to turn that newline off, which I'm not sure is possible.
I'll look into it more.
-Peff
next prev parent reply other threads:[~2009-07-18 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 23:16 [PATCH 0/2] cosmetic improvements for "git show tag" Jeff King
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 [this message]
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=20090718014743.GA16381@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nicolas.s.dev@gmx.fr \
/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).