From: Junio C Hamano <gitster@pobox.com>
To: Marcus Camen <mcamen@mcamen.de>
Cc: Mark Lodato <lodatom@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2009, #01; Mon, 06)
Date: Mon, 06 Jul 2009 15:34:01 -0700 [thread overview]
Message-ID: <7vd48djvae.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <200907070003.25788.mcamen@mcamen.de> (Marcus Camen's message of "Tue\, 7 Jul 2009 00\:03\:25 +0200")
Marcus Camen <mcamen@mcamen.de> writes:
>> - On a protected key/cert, with configuration, it asks the question
>> once.
>> - On an unprotected key/cert, without configuration, it never asks the
>> question.
>> - On an unprotected key/cert, with configuration, it asks an useless
>> question but it does so only once.
>>
>> You tested all of the above?
>
> Yes, all three tests run exactly as you described.
Wonderful; thanks.
next prev parent reply other threads:[~2009-07-06 22:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 18:32 What's cooking in git.git (Jul 2009, #01; Mon, 06) Junio C Hamano
2009-07-06 20:29 ` Marcus Camen
2009-07-06 21:38 ` Junio C Hamano
2009-07-06 22:03 ` Marcus Camen
2009-07-06 22:34 ` Junio C Hamano [this message]
2009-07-06 23:42 ` Jakub Narebski
2009-07-07 2:18 ` Mark Lodato
2009-07-07 21:11 ` Jeff King
2009-07-07 6:30 ` Johannes Sixt
2009-07-07 19:17 ` Linus Torvalds
2009-07-07 19:57 ` Alex Riesen
2009-07-07 22:13 ` Linus Torvalds
2009-07-07 20:08 ` Johannes Schindelin
2009-07-07 20:13 ` Shawn O. Pearce
2009-07-07 22:19 ` Junio C Hamano
2009-07-07 22:28 ` Shawn O. Pearce
2009-07-08 13:42 ` notes, was " Johannes Schindelin
2009-07-08 5:39 ` Stephen Boyd
2009-07-08 6:38 ` Johannes Sixt
2009-07-10 5:05 ` 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=7vd48djvae.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lodatom@gmail.com \
--cc=mcamen@mcamen.de \
/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).