Nelson Benitez Leon 2217c38e5b http: Avoid limit of retrying request only twice
Current code, after receiving HTTP_REAUTH, only retried
once, so couldn't do step 3 of the following sequence:

  1. We make a request; proxy returns 407, because we didn't give it a
     password. We ask for the password and return HTTP_REAUTH.

  2. We make another request; the proxy passes it to the actual server,
     who returns 401, because we didn't give an http password. We ask
     for the password and return HTTP_REAUTH.

  3. We make a third request, but this time everybody is happy.

Now we retry as long as we keep receiving HTTP_REAUTH, so the previous
sequence correctly completes.

Patch by Jeff King <peff@peff.net>

Signed-off-by: Nelson Benitez Leon <nbenitezl@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-03-15 13:48:08 -07:00
2012-03-01 20:59:25 -08:00
2012-01-03 13:48:00 -08:00
2012-03-01 20:59:41 -08:00
2012-01-31 22:24:23 -08:00
2011-12-13 22:53:08 -08:00
2011-10-21 16:04:32 -07:00
2012-02-23 13:30:14 -08:00
2012-01-06 12:44:07 -08:00
2012-02-17 07:59:55 -08:00
2012-02-28 13:25:57 -08:00
2012-02-10 12:53:55 -08:00
2012-01-08 15:08:03 -08:00
2011-10-07 15:46:14 -07:00
2011-12-16 22:33:40 -08:00
2011-08-11 12:21:07 -07:00
2012-02-26 17:39:04 -08:00
2011-09-19 20:46:48 -07:00
2012-02-12 19:24:47 -08:00
2012-02-26 16:40:20 -08:00
2012-01-08 15:07:20 -08:00
2012-02-26 16:42:35 -08:00
2011-12-19 16:06:41 -08:00
2012-02-05 23:53:21 -08:00
2011-08-20 22:33:57 -07:00
2012-02-28 12:23:26 +08:00
2012-01-06 12:44:07 -08:00
2012-01-06 12:44:07 -08:00
2011-08-22 10:07:07 -07:00
2011-11-06 20:31:28 -08:00
2011-12-16 22:33:40 -08:00
2012-02-20 00:15:11 -08:00
2012-01-06 12:44:07 -08:00
2011-12-12 16:09:38 -08:00
2011-11-07 22:12:19 -08:00
2012-02-12 19:50:39 -08:00
2012-02-12 19:50:39 -08:00
2012-02-22 18:17:39 -08:00
2012-02-22 18:17:39 -08:00
2011-11-12 22:27:38 -08:00
2011-12-11 23:16:24 -08:00
2012-02-26 23:05:45 -08:00
2012-02-22 18:17:39 -08:00
2011-12-11 23:16:25 -08:00
2011-10-17 21:37:15 -07:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git-scm.com/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org (read
Documentation/SubmittingPatches for instructions on patch submission).
To subscribe to the list, send an email with just "subscribe git" in
the body to majordomo@vger.kernel.org. The mailing list archives are
available at http://marc.theaimsgroup.com/?l=git and other archival
sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 678 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%