Jeff King 2cc7c2c737 setup: refactor repo format reading and verification
When we want to know if we're in a git repository of
reasonable vintage, we can call check_repository_format_gently(),
which does three things:

  1. Reads the config from the .git/config file.

  2. Verifies that the version info we read is sane.

  3. Writes some global variables based on this.

There are a few things we could improve here.

One is that steps 1 and 3 happen together. So if the
verification in step 2 fails, we still clobber the global
variables. This is especially bad if we go on to try another
repository directory; we may end up with a state of mixed
config variables.

The second is there's no way to ask about the repository
version for anything besides the main repository we're in.
git-init wants to do this, and it's possible that we would
want to start doing so for submodules (e.g., to find out
which ref backend they're using).

We can improve both by splitting the first two steps into
separate functions. Now check_repository_format_gently()
calls out to steps 1 and 2, and does 3 only if step 2
succeeds.

Note that the public interface for read_repository_format()
and what check_repository_format_gently() needs from it are
not quite the same, leading us to have an extra
read_repository_format_1() helper. The extra needs from
check_repository_format_gently() will go away in a future
patch, and we can simplify this then to just the public
interface.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-03-11 15:02:23 -08:00
2016-02-22 14:51:09 -08:00
2016-01-03 19:07:29 +09:00
2016-02-26 13:37:16 -08:00
2016-02-22 14:51:09 -08:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2016-02-26 13:37:16 -08:00
2015-10-05 12:30:19 -07:00
2015-11-20 08:02:05 -05:00
2016-02-26 13:37:16 -08:00
2016-02-22 14:51:09 -08:00
2015-08-03 11:01:21 -07:00
2015-08-03 11:01:27 -07:00
2016-03-11 15:02:23 -08:00
2016-02-26 13:37:23 -08:00
2016-01-18 19:48:43 -08:00
2016-02-26 13:37:16 -08:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-02-26 13:37:16 -08:00
2016-02-26 13:37:16 -08:00
2015-09-28 14:57:10 -07:00
2016-02-26 13:37:16 -08:00
2016-02-22 14:51:09 -08:00
2016-02-26 13:37:16 -08:00
2016-02-26 13:37:16 -08:00
2016-02-22 14:51:09 -08:00
2015-06-29 11:39:10 -07:00
2016-03-04 13:48:55 -08:00
2016-02-26 13:37:16 -08:00
2016-02-22 14:51:09 -08:00
2016-02-22 14:51:09 -08:00
2016-02-12 12:51:05 -08:00
2016-02-24 13:25:54 -08:00
2016-02-17 10:13:31 -08:00
2016-02-22 14:51:09 -08:00
2015-09-25 10:18:18 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-02-26 13:37:16 -08:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-02-24 13:26:01 -08:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2015-09-25 08:54:54 -07:00
2016-02-17 10:05:44 -08:00
2016-02-26 13:37:16 -08:00
2016-02-26 13:37:16 -08:00
2016-02-17 10:13:33 -08:00
2015-10-05 12:30:05 -07:00
2016-02-26 13:37:16 -08:00
2016-02-26 13:37:16 -08:00
2016-02-26 13:37:16 -08:00
2016-02-26 13:37:16 -08:00
2016-01-28 16:10:14 -08:00
2015-11-20 08:02:05 -05:00
2016-01-27 14:27:19 -08:00
2015-11-20 08:02:05 -05:00
2016-02-26 13:37:16 -08:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2015-08-11 14:29:36 -07:00
2016-02-22 10:40:35 -08:00
2016-01-19 11:22:29 -08:00
2016-02-26 13:37:16 -08:00

Git - fast, scalable, distributed revision control system

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 version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

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

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.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).

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://news.gmane.org/gmane.comp.version-control.git/, http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
Description
No description provided
Readme 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%