Martin Storsjö 3944ba0cb0 Allow curl to rewind the read buffers
When using multi-pass authentication methods, the curl library may
need to rewind the read buffers (depending on how much already has
been fed to the server) used for providing data to HTTP PUT, POST or
PROPFIND, and in order to allow the library to do so, we need to tell
it how by providing either an ioctl callback or a seek callback.

This patch adds an ioctl callback, which should be usable on older
curl versions (since 7.12.3) than the seek callback (introduced in
curl 7.18.0).

Some HTTP servers (such as Apache) give an 401 error reply immediately
after receiving the headers (so no data has been read from the read
buffers, and thus no rewinding is needed), but other servers (such
as Lighttpd) only replies after the whole request has been sent and
all data has been read from the read buffers, making rewinding necessary.

Signed-off-by: Martin Storsjo <martin@martin.st>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-04-02 13:04:07 -07:00
2009-03-30 13:29:57 -07:00
2008-12-17 21:56:48 -08:00
2009-04-01 22:49:28 -07:00
2009-02-10 21:32:10 -08:00
2008-07-19 11:25:51 -07:00
2008-06-30 22:45:50 -07:00
2008-07-19 11:17:43 -07:00
2007-05-30 15:03:50 -07:00
2007-06-07 00:04:01 -07:00
2008-08-28 20:50:10 -07:00
2009-03-14 13:36:34 -07:00
2009-03-26 00:28:46 -07:00
2009-03-14 13:36:34 -07:00
2008-08-03 14:14:10 -07:00
2009-03-26 00:26:25 -07:00
2009-03-14 13:36:34 -07:00
2009-01-28 11:33:51 -08:00
2008-09-15 23:11:35 -07:00
2008-09-25 09:39:24 -07:00
2009-02-13 17:27:58 -08:00
2009-02-13 17:27:58 -08:00
2009-02-10 21:32:10 -08:00
2009-01-28 11:33:03 -08:00
2009-03-26 00:26:25 -07:00
2009-03-14 13:36:34 -07:00
2008-10-10 08:39:20 -07:00
2008-10-10 08:39:20 -07:00
2009-01-17 18:30:41 -08:00
2009-03-17 18:54:31 -07:00
2009-03-28 01:16:46 -07:00
2008-11-02 16:36:40 -08:00
2009-03-20 14:30:51 -07:00
2008-02-25 23:57:35 -08:00
2009-02-26 23:06:38 -08:00
2008-08-05 21:21:08 -07:00
2009-02-05 19:40:35 -08:00
2008-07-13 14:12:48 -07:00
2009-03-15 13:05:05 -07:00
2008-09-25 08:00:28 -07:00
2008-09-07 23:52:16 -07:00
2009-04-02 13:04:07 -07:00
2009-04-02 13:04:07 -07:00
2009-03-14 13:36:34 -07:00
2008-11-23 19:23:34 -08:00
2009-04-01 22:46:31 -07:00
2008-10-25 12:09:31 -07:00
2009-03-14 13:36:34 -07:00
2009-03-26 00:28:46 -07:00
2009-03-21 23:21:15 -07:00
2009-02-14 21:27:35 -08:00
2009-02-14 21:27:35 -08:00
2008-07-21 19:11:50 -07:00
2009-03-20 09:35:32 -07:00
2008-03-02 15:11:07 -08:00
2005-11-02 16:50:58 -08:00
2006-03-25 16:35:43 -08:00
2009-01-17 18:30:41 -08:00
2007-05-01 02:59:08 -07:00
2009-03-26 00:28:46 -07:00
2009-02-10 22:26:37 -08:00
2009-01-21 23:52:16 -08:00
2009-02-04 16:30:43 -08:00
2009-02-04 16:30:43 -08:00
2009-02-10 22:26:37 -08: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.or.cz/
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. 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 603 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%