1
0
mirror of https://github.com/git/git.git synced 2025-04-14 23:56:01 +00:00
Jonathan Nieder 0316bba80f t9010: svnadmin can fail even if available
If svn is built against one version of SQLite and run against another,
libsvn_subr needlessly errors out in operations that need to make a
commit.

That is clearly not a bug in git but let us consider the ramifications for
the test suite.  git-svn uses libsvn directly and is probably broken by
that bug; it is right for git-svn tests to fail.  The vcs-svn lib, on the
other hand, does not use libsvn and the test t9010 only uses svn to check
its work.  This points to two possible improvements:

 - do not disable most vcs-svn tests if svn is missing.
 - skip validation rather than failing it when svn fails.

Bring about both by putting the svn invocations into a single test that
builds a repo to compare the test-svn-fe result against.  The test will
always pass but only will set the new SVNREPO test prereq if svn succeeds;
and validation using that repo gets an SVNREPO prerequisite so it only
runs with working svn installations.

Works-around: http://bugs.debian.org/608925
Noticed-by: A Large Angry SCM <gitzilla@gmail.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
2011-01-10 09:35:17 -08:00
2010-12-28 11:26:55 -08:00
2010-12-16 12:55:36 -08:00
2011-01-04 11:23:45 -08:00
2010-12-28 11:26:55 -08:00
2010-12-08 11:24:14 -08:00
2010-12-28 11:26:55 -08:00
2010-12-22 14:40:17 -08:00
2010-12-22 14:40:17 -08:00
2010-12-28 11:26:55 -08:00
2010-12-12 21:49:51 -08:00
2010-12-28 11:26:55 -08:00
2011-01-05 13:30:29 -08:00
2010-06-13 20:02:50 -07:00
2010-12-28 13:53:24 -08:00
2010-12-28 11:26:55 -08:00
2010-06-30 15:49:18 -07:00
2010-08-22 20:18:37 -07:00
2010-11-26 14:50:46 -08:00
2010-06-21 06:02:44 -07:00
2010-12-20 10:28:19 -08:00
2010-08-09 11:35:46 -07:00
2010-11-24 15:13:58 -08:00
2010-08-26 09:20:03 -07:00
2010-08-26 09:20:03 -07:00
2010-10-13 19:11:26 -07:00
2010-12-28 11:26:55 -08:00
2010-12-08 11:24:12 -08:00
2010-12-08 11:24:12 -08:00
2010-09-06 00:12:04 -07:00
2010-12-03 16:10:34 -08:00
2010-12-28 13:48:54 -08:00
2010-10-26 21:40:54 -07:00
2010-06-21 06:02:45 -07:00
2010-12-28 11:26:55 -08:00
2010-12-03 16:13:06 -08:00
2010-09-27 10:42:11 -07:00
2010-11-10 09:40:35 -08:00
2010-08-14 19:35:37 -07:00
2010-08-14 19:35:37 -07:00
2010-08-14 19:35:38 -07:00
2010-12-28 11:26:55 -08:00
2010-10-13 16:08:58 -07:00
2010-10-26 21:37:49 -07:00
2010-08-26 16:42:59 -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 829 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%