Kirill A. Korinskiy 753bc911f4 Remove the requirement opaquelocktoken uri scheme
The program flow of pushing over http is:

 - call lock_remote() to issue a DAV_LOCK request to the server to lock
   info/refs and branch refs being pushed into; handle_new_lock_ctx() is
   used to parse its response to populate "struct remote_lock" that is
   returned from lock_remote();

 - send objects;

 - call unlock_remote() to drop the lock.

The handle_new_lock_ctx() function assumed that the server will use a
lock token in opaquelocktoken URI scheme, which may have been an Ok
assumption under RFC 2518, but under RFC 4918 which obsoletes the older
standard it is not necessarily true.

This resulted in push failure (often resulted in "cannot lock existing
info/refs" error message) when talking to a server that does not use
opaquelocktoken URI scheme.

Signed-off-by: Kirill A. Korinskiy <catap@catap.ru>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-12-21 01:12:48 -08:00
2008-11-27 19:25:06 -08:00
2008-12-17 21:56:48 -08:00
2008-12-19 19:27:35 -08:00
2008-12-03 21:29:03 -08:00
2008-10-26 16:21:08 -07:00
2008-10-21 17:58:11 -07:00
2008-08-28 20:50:10 -07:00
2008-09-10 15:00:17 -07:00
2008-12-07 15:13:02 -08:00
2008-12-11 00:36:31 -08:00
2008-11-12 22:00:43 -08:00
2008-12-15 23:06:13 -08:00
2008-08-03 14:14:10 -07:00
2008-12-11 00:36:31 -08:00
2008-10-08 08:05:43 -07:00
2008-10-26 14:42:57 -07:00
2008-11-08 21:33:55 -08:00
2008-12-07 15:13:02 -08:00
2008-09-15 23:11:35 -07:00
2008-09-25 09:39:24 -07:00
2008-12-11 00:36:31 -08:00
2008-12-02 15:29:12 -08:00
2008-12-02 15:29:12 -08:00
2008-10-10 08:39:20 -07:00
2008-10-10 08:39:20 -07:00
2008-08-28 21:49:51 -07:00
2008-11-02 16:36:40 -08:00
2008-11-14 19:11:49 -08:00
2008-11-11 14:49:50 -08:00
2008-08-05 21:21:08 -07:00
2008-12-03 14:27:17 -08:00
2008-12-17 20:15:17 -08:00
2008-12-04 18:05:51 -08:00
2008-09-25 08:00:28 -07:00
2008-11-11 14:49:50 -08:00
2008-09-07 23:52:16 -07:00
2008-12-07 15:13:02 -08:00
2008-11-12 22:26:35 -08:00
2008-11-23 19:23:34 -08:00
2008-10-25 12:09:31 -07:00
2008-09-10 15:00:17 -07:00
2008-12-15 23:06:13 -08:00
2008-11-11 14:49:50 -08:00
2008-12-19 19:27:35 -08:00
2008-11-12 22:26:24 -08:00
2008-11-14 22:12:38 -08:00
2008-12-04 18:05:51 -08:00
2008-10-21 17:58:01 -07:00
2008-10-09 11:26:17 -07:00
2008-09-29 07:30:16 -07:00
2008-07-30 11:42:01 -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/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

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 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%