1
0
mirror of https://github.com/git/git.git synced 2025-03-25 06:51:50 +00:00
René Scharfe 22f0dcd963 archive-tar: split long paths more carefully
The name field of a tar header has a size of 100 characters.  This limit
was extended long ago in a backward compatible way by providing the
additional prefix field, which can hold 155 additional characters.  The
actual path is constructed at extraction time by concatenating the prefix
field, a slash and the name field.

get_path_prefix() is used to determine which slash in the path is used as
the cutting point and thus which part of it is placed into the field
prefix and which into the field name.  It tries to cram as much into the
prefix field as possible.  (And only if we can't fit a path into the
provided 255 characters we use a pax extended header to store it.)

If a path is longer than 100 but shorter than 156 characters and ends
with a slash (i.e. is for a directory) then get_path_prefix() puts the
whole path in the prefix field and leaves the name field empty.  GNU tar
reconstructs the path without complaint, but the tar included with
NetBSD 6 does not: It reports the header to be invalid.

For compatibility with this version of tar, make sure to never leave the
name field empty.  In order to do that, trim the trailing slash from the
part considered as possible prefix, if it exists -- that way the last
path component (or more, but not less) will end up in the name field.

Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-01-05 22:56:36 -08:00
2012-01-12 23:33:39 -08:00
2012-01-27 11:31:02 -08:00
2012-01-03 13:48:00 -08:00
2012-01-18 15:48:46 -08:00
2011-12-19 16:05:20 -08:00
2011-12-13 22:53:08 -08:00
2012-01-03 13:48:00 -08:00
2011-12-22 11:27:23 -08:00
2012-01-06 12:44:07 -08:00
2012-01-06 12:44:07 -08:00
2011-12-16 22:33:40 -08:00
2012-01-27 11:31:02 -08:00
2011-12-19 16:06:41 -08:00
2011-12-19 16:06:41 -08:00
2011-12-19 16:06:41 -08:00
2011-12-22 11:27:23 -08:00
2012-01-06 12:44:07 -08:00
2011-12-19 16:05:20 -08:00
2012-01-06 12:44:07 -08:00
2012-01-06 12:44:07 -08:00
2011-11-06 20:31:28 -08:00
2011-12-16 22:33:40 -08:00
2012-01-06 12:44:07 -08:00
2011-12-12 16:09:38 -08:00
2011-12-12 16:09:38 -08:00
2011-11-07 22:12:19 -08:00
2011-12-20 13:25:53 -08:00
2012-01-10 14:27:14 -08:00
2011-10-26 16:16:29 -07:00
2011-11-12 22:27:38 -08:00
2011-11-12 22:27:38 -08:00
2011-12-19 16:05:16 -08:00
2011-12-19 16:05:16 -08:00
2011-12-11 23:16:24 -08:00
2012-01-04 11:21:42 -08:00
2011-12-11 23:16:25 -08: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 798 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%