From: Ted Zlatanov <tzz@lifelogs.com>
To: git@vger.kernel.org
Subject: Re: [Wishlist] could git tell which password it is asking when asking a password.
Date: Fri, 01 Jul 2011 15:01:33 -0500 [thread overview]
Message-ID: <87aacxepnm.fsf@lifelogs.com> (raw)
In-Reply-To: 87tyb5n6pk.dlv@debian.org
On Fri, 01 Jul 2011 21:25:59 +0200 Rémi Vanicat <vanicat@debian.org> wrote:
RV> Junio C Hamano <gitster@pobox.com> writes:
>> I was wondering about that when I gave that quick patch. And "as a human"
>> may not necessarily apply when you are letting submodule fetch to recurse.
RV> I also believe that having the host name would be useful, both for human
RV> (another example would be git remote update when there are several
RV> remote) and script.
Maybe (using %U for the URL, %h for the host, %u for the user name):
"User name for %h: " OR "User name for %h (%U): "
"Password for %u@%h: " OR "Password for %u@%h (%U): "
with some way to switch between the two styles?
Ted
next prev parent reply other threads:[~2011-07-01 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 13:59 [Wishlist] could git tell which password it is asking when asking a password Rémi Vanicat
2011-07-01 17:00 ` Junio C Hamano
2011-07-01 17:16 ` Junio C Hamano
2011-07-01 17:18 ` Shawn Pearce
2011-07-01 17:50 ` Junio C Hamano
2011-07-01 19:25 ` Rémi Vanicat
2011-07-01 20:01 ` Ted Zlatanov [this message]
2011-07-01 20:30 ` Junio C Hamano
2011-07-01 20:48 ` Jeff King
2011-07-01 20:46 ` Jeff King
2011-07-01 17:04 ` Ted Zlatanov
2011-07-14 14:05 ` encrypted netrc for Git (was: [Wishlist] could git tell which password it is asking when asking a password.) Ted Zlatanov
2011-07-14 15:00 ` Jeff King
2011-07-15 17:08 ` encrypted netrc for Git Ted Zlatanov
2011-07-15 21:05 ` Jeff King
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=87aacxepnm.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=git@vger.kernel.org \
/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.