From: "Kyle Neath" <kneath@xxxxxxxxx>
Junio C Hamano <gitster@xxxxxxxxx> wrote:
If this were a new, insignificant, and obscure feature in a piece of
software with mere 20k users, it may be OK to release a new version with
the feature in an uncooked shape.
Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> wrote:
So, it's been a year or more that you've been aware of the importance of
this issue (from your/github's perspective), and we hear about it now,
at the end of the rc phase.
I apologize if it sounds like that. I've been discussing this situation
with
many people (including Jeff King) for a very long time now, and it was my
understanding that the credential caching was done and simply waiting for
a
new release. This is the first I've heard that it will not be included in
1.7.7, so I'm voicing my opinion now. Admittedly, late in the game - and I
apologize for that.
I'd be happy to help in any capacity I can. Unfortunately I'm no C hacker,
and
I've accepted that as a character flaw (it's something I'm working on).
I'm
afraid I can't be of much help with the actual code. What I can provide is
an
alternate viewpoint to the core team. A viewpoint of someone who's spent 3
years trying to make git easier for newcomers.
Help in any capacity :
Would it not be possible for GitHub to provide for those key users such a
trial version
that includes the patches identified to obtain the "real-world success
reports" that
are needed, as mentioned in the "Re: What's cooking in git.git (Aug 2011,
#07; Wed, 24)"
This should help satisfy the needs from both sides, even if you can only
push it to a few clients.
What's cooking in git.git (Aug 2011, #07; Wed, 24)
Looked mostly reasonable except for the limitation that it is not clear
how to deal with a site at which a user needs to use different passwords
for different repositories. Will keep it in "next" at least for one
cycle,
until we start hearing real-world success reports on the list.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html