From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Erik Faye-Lund <kusmabite@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2011, #02; Mon, 5)
Date: Tue, 6 Dec 2011 13:47:26 -0500 [thread overview]
Message-ID: <20111206184726.GA9492@sigill.intra.peff.net> (raw)
In-Reply-To: <7vhb1dh7ki.fsf@alter.siamese.dyndns.org>
On Tue, Dec 06, 2011 at 10:35:25AM -0800, Junio C Hamano wrote:
> > Also, let's drop the top git_getpass bits from the topic for now (they
> > will not be part of my rebase). They are a separate topic that can go on
> > top, but I think there was some question from Erik of whether we should
> > simply roll our own getpass().
>
> Sounds sensible.
>
> I suspect that there may be a codepath where we could ask both username
> and password; instead of making two consecutive calls to getpass() or
> git_prompt(), the series may want to give a higher level abstraction, so
> that GUI can show a dialog with two input fields (single-line input and
> password input) and interact only once with the user. Such an input widget
> could _show_ the username, and optionally even let it edited (there may be
> ramifications depending on how the codepath uses the username), while
> asking for the corresponding password.
Yes, I've considered that, too. But I think the idea of a combined
username/password is part of the credential code, and the right
call chain is something like:
credential_fill
-> call helpers with "get"; return if it works
-> credential_getpass
-> call helpers with "ask" for combined GUI prompt
-> otherwise, use git_prompt
-> git_prompt("username")
-> git_prompt("password")
So the "switch getpass to a generic prompt" idea is separate from
providing that higher-level abstraction.
> >> * jk/maint-1.6.2-upload-archive (2011-11-21) 1 commit
> >> - archive: don't let remote clients get unreachable commits
> >> (this branch is used by jk/maint-upload-archive.)
> [...]
> I was planning to first have the really tight version graduate to 'master'
> and ship it in 1.7.9, while possibly merging that to 1.7.8.X series. If we
> hear complaints from real users in the meantime before or after such
> releases, we could apply loosening patch on top of these topics and call
> them "regression fix", but I have been assuming that nobody would have
> been using this backdoor for anything that really matters.
OK. I'll hold back on the loosening then.
-Peff
next prev parent reply other threads:[~2011-12-06 18:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 5:01 What's cooking in git.git (Dec 2011, #02; Mon, 5) Junio C Hamano
2011-12-06 5:35 ` Ramkumar Ramachandra
2011-12-06 18:20 ` Junio C Hamano
2011-12-06 20:30 ` Ramkumar Ramachandra
2011-12-07 10:08 ` &&-chaining tester Jonathan Nieder
2011-12-07 19:36 ` Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 01/15] t1013 (loose-object-format): fix && chaining Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 02/15] t1300 (repo-config): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 03/15] t1412 (reflog-loop): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 04/15] t1007 (hash-object): " Ramkumar Ramachandra
2011-12-07 21:47 ` Jonathan Nieder
2011-12-08 4:42 ` Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 05/15] t1510 (repo-setup): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 06/15] t1511 (rev-parse-caret): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 07/15] t1510 (worktree): " Ramkumar Ramachandra
2011-12-07 21:51 ` Jonathan Nieder
2011-12-08 4:39 ` Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 08/15] t3200 (branch): " Ramkumar Ramachandra
2011-12-07 21:55 ` Jonathan Nieder
2011-12-08 4:47 ` Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 09/15] t3418 (rebase-continue): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 10/15] t3400 (rebase): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 11/15] t3310 (notes-merge-manual-resolve): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 12/15] t3419 (rebase-patch-id): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 13/15] t3030 (merge-recursive): use test_expect_code Ramkumar Ramachandra
2011-12-07 21:57 ` Jonathan Nieder
2011-12-07 19:36 ` [PATCH 14/15] t1006 (cat-file): use test_cmp Ramkumar Ramachandra
2011-12-07 22:01 ` Jonathan Nieder
2011-12-07 19:36 ` [PATCH 15/15] t3040 (subprojects-basic): modernize style Ramkumar Ramachandra
2011-12-07 22:21 ` Jonathan Nieder
2011-12-08 13:04 ` Ramkumar Ramachandra
2011-12-08 8:06 ` &&-chaining tester Matthieu Moy
2011-12-08 18:19 ` What's cooking in git.git (Dec 2011, #02; Mon, 5) Junio C Hamano
2011-12-06 5:52 ` Jeff King
2011-12-06 11:22 ` Erik Faye-Lund
2011-12-06 18:52 ` Jeff King
2011-12-08 19:44 ` Erik Faye-Lund
2011-12-08 21:25 ` Junio C Hamano
2011-12-06 18:35 ` Junio C Hamano
2011-12-06 18:47 ` Jeff King [this message]
2011-12-06 11:20 ` Nguyen Thai Ngoc Duy
2011-12-06 19:10 ` Junio C Hamano
2011-12-06 14:01 ` Nguyen Thai Ngoc Duy
2011-12-06 19:12 ` Junio C Hamano
2011-12-06 21:12 ` Luke Diamand
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=20111206184726.GA9492@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kusmabite@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).