From: Junio C Hamano <gitster@pobox.com>
To: Nsengiyumva Wilberforce <nsengiyumvawilberforce@gmail.com>
Cc: git@vger.kernel.org, Hariom Verma <hariom18599@gmail.com>,
Jaydeep Das <jaydeepjd.8914@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH v5 1/1] ref-filter: add new "signature" atom
Date: Tue, 14 Mar 2023 15:51:31 -0700 [thread overview]
Message-ID: <xmqqpm9bosjw.fsf@gitster.g> (raw)
In-Reply-To: <20230311210607.64927-2-nsengiyumvawilberforce@gmail.com> (Nsengiyumva Wilberforce's message of "Sat, 11 Mar 2023 16:06:07 -0500")
Nsengiyumva Wilberforce <nsengiyumvawilberforce@gmail.com> writes:
> Co-authored-by: Hariom Verma <hariom18599@gmail.com>
> Co-authored-by: Jaydeep Das <jaydeepjd.8914@gmail.com>
> Mentored-by: Christian Couder <chriscool@tuxfamily.org>
> Mentored-by: Hariom Verma <hariom18599@gmail.com>
> Signed-off-by: Nsengiyumva Wilberforce <nsengiyumvawilberforce@gmail.com>
https://github.com/git/git/actions/runs/4410308954/jobs/7727652857#step:6:1898
+ git for-each-ref refs/heads/signed --format=%(signature)
+ test_cmp expected actual
+ test 2 -ne 2
+ eval diff -u "$@"
+ diff -u expected actual
--- expected2023-03-13 23:08:51.495987174 +0000
+++ actual2023-03-13 23:08:51.519986953 +0000
@@ -1,5 +1,4 @@
gpg: Signature made Mon Mar 13 23:08:51 2023 UTC
gpg: using DSA key 13B6F51ECDDE430D
-gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: Good signature from "C O Mitter <committer@example.com>"
error: last command exited with $?=1
not ok 342 - test bare signature atom
+ git for-each-ref refs/heads/signed --format=%(signature)
+ test_cmp expected actual
+ test 2 -ne 2
+ eval diff -u "$@"
+ diff -u expected actual
--- expected
+++ actual
@@ -1,5 +1,4 @@
gpg: Signature made Mon Mar 13 23:08:51 2023 UTC
gpg: using DSA key 13B6F51ECDDE430D
-gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: Good signature from "C O Mitter <committer@example.com>"
error: last command exited with $?=1
not ok 342 - test bare signature atom
Are there differences between versions of GPG that, for the purpose
of the testing, we do not care?
next prev parent reply other threads:[~2023-03-14 22:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 0:55 [PATCH] ref-filter: add new atom "signature" atom nsengaw4c via GitGitGadget
2022-12-27 2:20 ` Junio C Hamano
2023-01-02 4:49 ` NSENGIYUMVA WILBERFORCE
2023-01-02 8:37 ` Christian Couder
2023-01-03 0:58 ` Junio C Hamano
[not found] ` <CA+PPyiGd0-AiwhPa5e+fDdA9RybS+c5XeOYm5yycCZco3VHAxg@mail.gmail.com>
2023-01-08 15:21 ` NSENGIYUMVA WILBERFORCE
2022-12-27 6:11 ` Jeff King
2023-01-02 6:34 ` NSENGIYUMVA WILBERFORCE
2023-01-10 0:52 ` [PATCH v3 0/1] ref-filter: add new " Nsengiyumva Wilberforce
2023-01-10 0:52 ` [PATCH v3 1/1] " Nsengiyumva Wilberforce
2023-01-16 17:38 ` [PATCH v4 0/1] " Nsengiyumva Wilberforce
2023-01-16 17:38 ` [PATCH v4 1/1] " Nsengiyumva Wilberforce
2023-03-11 21:06 ` [PATCH v5 0/1] " Nsengiyumva Wilberforce
2023-03-11 21:06 ` [PATCH v5 1/1] " Nsengiyumva Wilberforce
2023-03-14 22:51 ` Junio C Hamano [this message]
2023-04-28 18:29 ` Kousik Sanagavarapu
2023-04-29 18:37 ` Kousik Sanagavarapu
2023-01-26 21:07 ` [PATCH v4 0/1] " Junio C Hamano
2023-01-10 9:13 ` [PATCH v3 " Christian Couder
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=xmqqpm9bosjw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=jaydeepjd.8914@gmail.com \
--cc=nsengiyumvawilberforce@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.