From: Junio C Hamano <gitster@pobox.com>
To: Mischa POSLAWSKY <git@shiar.nl>
Cc: git@vger.kernel.org, "Оля Тележная" <olyatelezhnaya@gmail.com>
Subject: Re: [PATCH 2/1] t6300: format missing tagger
Date: Thu, 22 Aug 2019 09:15:55 -0700 [thread overview]
Message-ID: <xmqq36htqipw.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190822135528.GB28725@shiar.net> (Mischa POSLAWSKY's message of "Thu, 22 Aug 2019 15:55:28 +0200")
Mischa POSLAWSKY <git@shiar.nl> writes:
> Alright, thanks for the pointer.
> Here's a batch of tests on all pertaining atoms.
Good to see that you made it much more thorough than my q-n-d
illustration patch ;-)
> -- >8 --
>
> Strip an annotated tag of its tagger header and verify it's ignored
> correctly in all cases, as fixed in commit e2a81276e8 (ref-filter:
> initialize empty name or email fields, 2019-08-19).
I am inclined to squash this test part of the update into the said
commit; you'd lose one commit count, but hopefully you do not mind?
My motivation for doing so is that it would allow us to lose the "as
fixed in commit X" comment in a log message, which in turn would
mean that the code-fix patch can later be rebased safely without
having to remember that this one needs to be adjusted ("git rebase"
does not do such a rewrite for us, and I personally do not think
"git rebase" should do such a rewrite silently, as I cannot quantify
the risk of false positives).
>
> Signed-off-by: Mischa POSLAWSKY <git@shiar.nl>
> ---
> t/t6300-for-each-ref.sh | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/t/t6300-for-each-ref.sh b/t/t6300-for-each-ref.sh
> index ab69aa176d..9c910ce746 100755
> --- a/t/t6300-for-each-ref.sh
> +++ b/t/t6300-for-each-ref.sh
> @@ -526,6 +526,25 @@ test_expect_success 'Check ambiguous head and tag refs II (loose)' '
> test_cmp expected actual
> '
>
> +test_expect_success 'create tag without tagger' '
> + git tag -a -m "Broken tag" taggerless &&
> + git tag -f taggerless $(git cat-file tag taggerless |
> + sed -e "/^tagger /d" |
> + git hash-object --stdin -w -t tag)
> +'
> +
> +test_atom refs/tags/taggerless type 'commit'
> +test_atom refs/tags/taggerless tag 'taggerless'
> +test_atom refs/tags/taggerless tagger ''
> +test_atom refs/tags/taggerless taggername ''
> +test_atom refs/tags/taggerless taggeremail ''
> +test_atom refs/tags/taggerless taggerdate ''
> +test_atom refs/tags/taggerless committer ''
> +test_atom refs/tags/taggerless committername ''
> +test_atom refs/tags/taggerless committeremail ''
> +test_atom refs/tags/taggerless committerdate ''
> +test_atom refs/tags/taggerless subject 'Broken tag'
> +
> test_expect_success 'an unusual tag with an incomplete line' '
>
> git tag -m "bogo" bogo &&
next prev parent reply other threads:[~2019-08-22 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 21:51 [PATCH] ref-filter: initialize empty name or email fields Mischa POSLAWSKY
2019-08-19 17:55 ` Junio C Hamano
2019-08-20 16:37 ` Junio C Hamano
2019-08-22 13:23 ` Mischa POSLAWSKY
2019-08-21 21:57 ` Junio C Hamano
2019-08-22 13:55 ` [PATCH 2/1] t6300: format missing tagger Mischa POSLAWSKY
2019-08-22 16:15 ` Junio C Hamano [this message]
2019-08-22 16:27 ` Mischa POSLAWSKY
2019-08-22 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
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=xmqq36htqipw.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@shiar.nl \
--cc=git@vger.kernel.org \
--cc=olyatelezhnaya@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).