git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Knut Franke <k.franke@science-computing.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Frank Li <lznuaa@gmail.com>
Subject: Re: [PATCH 1/2] Add a new option 'core.askpass'.
Date: Mon, 30 Aug 2010 08:56:58 -0500	[thread overview]
Message-ID: <20100830135658.GC2315@burratino> (raw)
In-Reply-To: <201008301344.22983.k.franke@science-computing.de>

Knut Franke wrote:
> On Friday 27 August 2010 19:28:38 Junio C Hamano wrote:

>> Also this
>> does not feel like a "core." thing, but it may be just me.
>
> Where else could it go? It's not entirely http specific:
>
> $ grep git_getpass *.c
> connect.c:char *git_getpass(const char *prompt)
> http.c:                 user_pass = xstrdup(git_getpass("Password: "));
> http.c: ssl_cert_password = git_getpass("Certificate Password: ");
> http.c:                          * git_getpass is needed here because its very likely stdin/stdout are
> http.c:                          * but that is non-portable.  Using git_getpass() can at least be stubbed
> http.c:                         user_name = xstrdup(git_getpass("Username: "));
> imap-send.c:                    arg = git_getpass(prompt);
>
> Nor does it relate to a single command.

Perhaps "push.askpass" and "imap.askpass", maybe with the latter
defaulting to the former or something?  This would help preserve
the illusion that the git commands are sort of independent tools.

Haven't thought deeply about it at all, though.

  parent reply	other threads:[~2010-08-30 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 10:51 [PATCH 1/2] Add a new option 'core.askpass' Knut Franke
2010-08-27 17:28 ` Junio C Hamano
2010-08-30 11:44   ` Knut Franke
2010-08-30 12:17     ` Erik Faye-Lund
2010-08-30 13:56     ` Jonathan Nieder [this message]
2010-08-30 14:17       ` Jonathan Nieder

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=20100830135658.GC2315@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=k.franke@science-computing.de \
    --cc=lznuaa@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 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).