1
0
mirror of https://github.com/git/git.git synced 2025-04-21 01:57:11 +00:00
David Aguilar cfe2d4be91 difftool: ignore symbolic links in use_wt_file
The caller is preparing a narrowed-down copy of the working tree and
this function is asked if the path should be included in that copy.
If we say yes, the path from the working tree will be either symlinked
or copied into the narrowed-down copy.

For any path that is a symbolic link, the caller later fixes up the
narrowed-down copy by unlinking the path and replacing it with a
regular file it writes out that mimics the way how "git diff"
compares symbolic links.

Let's answer "no, you do not want to copy/symlink the working tree
file" for all symbolic links from this function, as we know the
result will not be used because it will be overwritten anyway.

Incidentally, this also stops the function from feeding a symbolic
link in the working tree to hash-object, which is a wrong thing to
do to begin with. The link may be pointing at a directory, or worse
may be dangling (both would be noticed as an error).  Even if the
link points at a regular file, hashing the contents of a file that
is pointed at by the link is not correct (Git hashes the contents of
the link itself, not the pointee).

Signed-off-by: David Aguilar <davvid@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-10-29 13:43:10 -07:00
2015-09-04 10:26:23 -07:00
2014-11-28 19:08:50 +01:00
2014-10-08 13:05:26 -07:00
2014-12-17 11:46:57 -08:00
2014-10-08 13:05:25 -07:00
2014-09-19 11:38:35 -07:00
2014-12-17 11:46:57 -08:00
2014-10-20 12:23:48 -07:00
2014-12-17 11:42:28 -08:00
2014-12-17 11:46:57 -08:00
2014-10-29 10:08:07 -07:00
2015-09-04 10:26:23 -07:00
2014-10-20 12:25:32 -07:00
2014-10-08 13:05:25 -07:00
2014-09-29 12:36:11 -07:00
2014-10-31 11:49:47 -07:00
2014-10-20 12:23:48 -07:00
2014-10-20 12:23:48 -07:00
2014-10-14 10:49:45 -07:00
2015-09-04 09:36:28 -07:00
2014-10-19 15:28:30 -07:00
2014-10-19 15:28:30 -07:00
2014-12-17 11:46:57 -08:00
2014-10-20 12:23:48 -07:00
2014-12-17 11:46:57 -08:00
2014-10-10 16:02:26 -07:00
2015-09-04 10:26:23 -07:00
2014-10-08 13:05:25 -07:00
2014-10-08 13:05:25 -07:00
2014-10-24 14:59:10 -07:00
2014-11-19 13:47:52 -08:00
2015-01-07 13:28:10 -08:00
2014-12-17 11:04:39 -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 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.

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).

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 (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.
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%