1
0
mirror of https://github.com/git/git.git synced 2025-03-22 19:16:32 +00:00
Junio C Hamano 5bf29b9500 read_sha1_file(): allow selective bypassing of replacement mechanism
The way "object replacement" mechanism was tucked to the read_sha1_file()
interface was suboptimal in a couple of ways:

 - Callers that want it to die with useful diagnosis upon seeing a corrupt
   object does not have a way to say that they do not want any object
   replacement.

 - Callers who do not want it to die but want to handle the errors
   themselves are told to arrange to call read_object(), but the function
   does not use the replacement mechanism, and also it is a file scope
   static function that not many callers can call to begin with.

This adds a read_sha1_file_extended() that takes a set of flags; the
callers of read_sha1_file() passes a flag READ_SHA1_FILE_REPLACE to ask
for object replacement mechanism to kick in.

Later, we could add another flag bit to tell the function to return an
error instead of dying and then remove the misguided "call read_object()
yourself".

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-05-15 15:23:34 -07:00
2011-03-26 10:42:35 -07:00
2011-04-27 11:36:42 -07:00
2011-04-28 14:11:39 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2011-03-17 15:30:49 -07:00
2011-02-13 15:13:41 -08:00
2011-02-06 22:50:26 -08:00
2011-03-28 10:54:54 -07:00
2011-03-22 10:16:54 -07:00
2010-05-07 09:34:27 -07:00
2011-05-06 10:50:06 -07:00
2011-05-02 15:58:30 -07:00
2011-02-26 01:06:50 -08:00
2011-04-03 13:53:11 -07:00
2011-04-28 14:11:39 -07:00
2011-04-28 14:11:39 -07:00
2010-06-13 20:02:50 -07:00
2011-05-04 15:47:40 -07:00
2011-05-06 11:00:46 -07:00
2010-06-30 15:49:18 -07:00
2010-01-21 20:03:45 -08:00
2010-12-20 10:28:19 -08:00
2010-11-24 15:13:58 -08:00
2010-08-26 09:20:03 -07:00
2010-10-13 19:11:26 -07:00
2010-01-12 01:06:09 -08:00
2011-05-06 11:00:46 -07:00
2010-04-01 23:58:30 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-02-07 15:15:17 -08:00
2011-03-22 11:43:27 -07:00
2011-04-29 11:47:35 -07:00
2011-02-16 13:20:50 -08:00
2011-05-02 15:58:30 -07:00
2010-05-04 15:38:58 -07:00
2010-01-21 20:03:45 -08:00
2011-04-27 11:36:43 -07:00
2011-02-21 22:51:07 -08:00
2011-02-07 15:04:42 -08:00
2010-08-14 19:35:37 -07:00
2011-03-22 11:43:27 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 11:43:27 -07:00
2011-03-22 21:37:53 -07:00
2011-05-06 10:50:06 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-02-09 16:41:17 -08:00
2010-04-02 00:05:31 -07:00
2011-04-01 17:55:55 -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 797 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%