git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos Rica" <jasampler@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] t7004: ship trustdb to avoid gpg warnings
Date: Sun, 1 Jul 2007 14:52:47 +0200	[thread overview]
Message-ID: <1b46aba20707010552k3ca46dbfj6ef508440dee6214@mail.gmail.com> (raw)
In-Reply-To: <7v1wfsak92.fsf@assigned-by-dhcp.cox.net>

We finally supplied every file generated by gpg. I talked a lot with
Johannes about what files could be safely threw away and I even ask
that in the #gnupg channel to remove this file. I hadn't seen those
messages.

The patch worked fine for me. Indeed, I realized that the file is
equal to that I shipped in the first version of the tests.

Thank you Junio for your effort on this.

2007/7/1, Junio C Hamano <gitster@pobox.com>:
> This avoids warning messages from gpg while verifying the tags; without it,
> the program complains that the key is not certified with a trusted signature.
>
> ---
>  t/t7004/trustdb.gpg |  Bin 0 -> 1280 bytes
>  1 files changed, 0 insertions(+), 0 deletions(-)
>  create mode 100644 t/t7004/trustdb.gpg
>
> diff --git a/t/t7004/trustdb.gpg b/t/t7004/trustdb.gpg
> new file mode 100644
> index 0000000000000000000000000000000000000000..abace962b8bf84be688a6f27e4ebd0ee7052f210
> GIT binary patch
> literal 1280
> zcmZQfFGy!*W@Ke#U|?`dKkWykumMIcY@%4iM%7^n6rj+M4;MLzzlOX&pwTnxkD-}P
> zc^HbXN0fL!SIq1?>env3?W^3`d(OOU5YNaX{KU(k^<0;M@87ONv)_6ZxD={-=<kYO
> M2Ud3=2BC}r0AuhNr2qf`
>
> literal 0
> HcmV?d00001
>
> --
> 1.5.2
>
>
>

  reply	other threads:[~2007-07-01 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0706301956240.4438@racer.site>
2007-07-01  3:14 ` [PATCH] t7004: ship trustdb to avoid gpg warnings Junio C Hamano
2007-07-01 12:52   ` Carlos Rica [this message]
2007-07-01 18:19     ` 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=1b46aba20707010552k3ca46dbfj6ef508440dee6214@mail.gmail.com \
    --to=jasampler@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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).