1
0
mirror of https://github.com/git/git.git synced 2025-03-26 02:56:25 +00:00
Marcel M. Cary 08fc060865 git-sh-setup: Fix scripts whose PWD is a symlink into a git work-dir
I want directories of my working tree to be linked to from various
paths on my filesystem where third-party components expect them, both
in development and production environments.  A build system's install
step could solve this, but I develop scripts and web pages that don't
need to be built.  Git's submodule system could solve this, but we
tend to develop, branch, and test those directories all in unison, so
one big repository feels more natural.  We prefer to edit and commit
on the symlinked paths, not the canonical ones, and in that setting,
"git pull" fails to find the top-level directory of the repository
while other commands work fine.

"git pull" fails because POSIX shells have a notion of current working
directory that is different from getcwd().  The shell stores this path
in PWD.  As a result, "cd ../" can be interpreted differently in a
shell script than chdir("../") in a C program.  The shell interprets
"../" by essentially stripping the last textual path component from
PWD, whereas C chdir() follows the ".." link in the current directory
on the filesystem.  When PWD is a symlink, these are different
destinations.  As a result, Git's C commands find the correct
top-level working tree, and shell scripts do not.

Changes:

* When interpreting a relative upward (../) path in cd_to_toplevel,
  prepend the cwd without symlinks, given by /bin/pwd
* Add tests for cd_to_toplevel and "git pull" in a symlinked
  directory that failed before this fix, plus contrasting scenarios
  that already worked

Signed-off-by: Marcel M. Cary <marcel@oak.homeunix.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-12-21 01:10:48 -08:00
2008-11-27 19:25:06 -08:00
2008-12-17 21:56:48 -08:00
2008-12-19 19:27:35 -08:00
2008-12-03 21:29:03 -08:00
2008-10-26 16:21:08 -07:00
2008-10-21 17:58:11 -07:00
2008-12-07 15:13:02 -08:00
2008-12-11 00:36:31 -08:00
2008-11-12 22:00:43 -08:00
2008-12-15 23:06:13 -08:00
2008-12-11 00:36:31 -08:00
2008-10-26 14:42:57 -07:00
2008-11-08 21:33:55 -08:00
2008-12-07 15:13:02 -08:00
2008-12-11 00:36:31 -08:00
2008-12-02 15:29:12 -08:00
2008-12-02 15:29:12 -08:00
2008-11-02 16:36:40 -08:00
2008-11-14 19:11:49 -08:00
2008-11-11 14:49:50 -08:00
2008-12-03 14:27:17 -08:00
2008-12-17 20:15:17 -08:00
2008-12-04 18:05:51 -08:00
2008-11-11 14:49:50 -08:00
2008-12-07 15:13:02 -08:00
2008-11-12 22:26:35 -08:00
2008-11-23 19:23:34 -08:00
2008-10-25 12:09:31 -07:00
2008-12-15 23:06:13 -08:00
2008-11-11 14:49:50 -08:00
2008-12-19 19:27:35 -08:00
2008-11-12 22:26:24 -08:00
2008-11-14 22:12:38 -08:00
2008-12-04 18:05:51 -08:00
2008-10-21 17:58:01 -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/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
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 799 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%