1
0
mirror of https://github.com/git/git.git synced 2025-04-21 22:37:52 +00:00
Shawn O. Pearce 7da4e2280c test smart http fetch and push
The top level directory "/smart/" of the test Apache server is mapped
through our git-http-backend CGI, but uses the same underlying
repository space as the server's document root.  This is the most
simple installation possible.

Server logs are checked to verify the client has accessed only the
smart URLs during the test.  During fetch testing the headers are
also logged from libcurl to ensure we are making a reasonably sane
HTTP request, and getting back reasonably sane response headers
from the CGI.

When validating the request headers used during smart fetch we munge
away the actual Content-Length and replace it with the placeholder
"xxx".  This avoids unnecessary varability in the test caused by
an unrelated change in the requested capabilities in the first want
line of the request.  However, we still want to look for and verify
that Content-Length was used, because smaller payloads should be
using Content-Length and not "Transfer-Encoding: chunked".

When validating the server response headers we must discard both
Content-Length and Transfer-Encoding, as Apache2 can use either
format to return our response.

During development of this test I observed Apache returning both
forms, depending on when the processes got CPU time.  If our CGI
returned the pack data quickly, Apache just buffered the whole
thing and returned a Content-Length.  If our CGI took just a bit
too long to complete, Apache flushed its buffer and instead used
"Transfer-Encoding: chunked".

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-11-04 17:58:16 -08:00
2009-10-09 00:02:23 -07:00
2009-08-31 22:09:53 -07:00
2009-11-04 17:58:16 -08:00
2009-09-14 02:23:36 -07:00
2009-06-30 16:12:24 -07:00
2009-06-18 09:22:46 -07:00
2009-08-21 18:47:53 -07:00
2009-09-13 01:30:53 -07:00
2009-08-05 12:39:33 -07:00
2009-10-04 14:48:51 -07:00
2009-08-07 22:35:17 -07:00
2009-10-30 19:20:53 -07:00
2009-07-22 21:56:46 -07:00
2009-09-13 01:33:18 -07:00
2009-10-30 19:20:53 -07:00
2009-09-13 01:32:26 -07:00
2009-07-06 09:39:46 -07:00
2009-10-03 06:04:38 -04:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2009-08-28 19:38:19 -07:00
2009-10-11 21:54:44 -07:00
2009-08-21 18:47:53 -07:00
2009-10-10 00:05:19 -07:00
2009-09-13 01:31:55 -07:00
2009-07-02 21:36:42 -07:00
2009-09-13 01:30:53 -07:00
2009-09-18 20:00:42 -07:00
2009-08-05 18:37:12 -07:00
2009-11-04 17:58:15 -08:00
2009-11-04 17:58:15 -08:00
2009-10-12 16:22:35 -07:00
2009-08-21 18:47:53 -07:00
2009-09-18 20:00:42 -07:00
2009-08-21 18:47:53 -07:00
2009-09-16 14:53:26 -07:00
2009-11-04 17:58:15 -08:00
2009-06-20 21:47:27 -07:00
2009-11-04 17:58:15 -08:00
2009-09-18 20:00:42 -07:00
2009-11-04 17:58:15 -08:00
2009-08-30 22:04:46 -07:00
2009-11-04 17:58:15 -08:00
2009-07-18 16:57:47 -07:00
2009-10-01 04:12:21 -04:00
2009-07-22 21:57:41 -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. 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
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 866 MiB
Languages
C 49.9%
Shell 38.6%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%