From: "Carlos Rica" <jasampler@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] "git-tag -s" should create a signed annotated tag
Date: Mon, 26 Nov 2007 05:51:47 +0100 [thread overview]
Message-ID: <1b46aba20711252051x5ec7398er6806f21e179583d4@mail.gmail.com> (raw)
In-Reply-To: <7vprxxj4hl.fsf@gitster.siamese.dyndns.org>
On Nov 26, 2007 12:21 AM, Junio C Hamano <gitster@pobox.com> wrote:
> The earlier patch 396865859918e9c7bf8ce74aae137c57da134610 (Make
> builtin-tag.c use parse_options.) broke "git-tag -s".
>
> * It's _very_ disturbing that the testsuite did not catch this
> breakage, even though I though we had a very detailed coverage for
> "git tag" when it was rewritten in C.
Yes, you're right, "-s" without -m or -F is creating lightweight tags
in my proposal.
I think it is due to the absence of tests checking the "editor" option, that is,
calls without -m or -F options to provide the message, since the tests are using
only those and they are enabling automatically the creation of annotated tags.
I need to think in adding tests replacing the editor with a custom command
to check also the correct behaviour of git-tag when the EDITOR and/or
the other variables are set.
At the end, I've learned that it's better to test a little of every feature than
test completely only a few of them.
Thank you.
prev parent reply other threads:[~2007-11-26 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 23:21 [PATCH] "git-tag -s" should create a signed annotated tag Junio C Hamano
2007-11-26 4:50 ` Jeff King
2007-11-26 4:51 ` Carlos Rica [this message]
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=1b46aba20711252051x5ec7398er6806f21e179583d4@mail.gmail.com \
--to=jasampler@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).