Re: Symbolic link documentation
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 17 quoted lines
> On Thu, 20 Sep 2007, Matt Seitz (matseitz) wrote:
>
> > Where does the git user documentation discuss how git handles symbolic
> > links?
>
> $ git grep symbolic Documentation/ | grep link
> Documentation/RelNotes-1.5.0.2.txt: in place of the symbolic link. The default strategy,
> Documentation/RelNotes-1.5.0.2.txt: that was pointed at by the symbolic link. Both of these
> Documentation/RelNotes-1.5.0.2.txt: when changes to a symbolic link conflicted. It should have
> Documentation/RelNotes-1.5.0.2.txt: file the symbolic link pointed at.
> Documentation/RelNotes-1.5.1.5.txt: directory $PWD points at is a symbolic link.
> Documentation/RelNotes-1.5.1.6.txt: directory $PWD points at is a symbolic link.
> Documentation/RelNotes-1.5.1.txt: in place of the symbolic link. The default strategy,
> Documentation/RelNotes-1.5.1.txt: that was pointed at by the symbolic link. Both of these
> Documentation/RelNotes-1.5.1.txt: when changes to a symbolic link conflicted. It should have
> Documentation/RelNotes-1.5.1.txt: file the symbolic link pointed at.
> Documentation/RelNotes-1.5.3.2.txt: - an untracked symbolic link to a directory made it fart;
Many of these release notes are talking about bugs that we fixed related to switching between revisions where in one revision the path was a symlink and in the other revision it was a directory or a file (or vice-versa).
Show 5 quoted lines
> Documentation/config.txt: If false, symbolic links are checked out as small plain files that
> Documentation/config.txt: symbolic links. True by default.
> Documentation/git-update-index.txt:to 'false' (see gitlink:git-config[1]), symbolic links are checked out
> Documentation/git-update-index.txt:from symbolic link to regular file.
> Documentation/technical/racy-git.txt:files vs symbolic links) and executable bits (only for regular
These are probably what Matt was looking for.
Show 10 quoted lines
> Documentation/config.txt: and other symbolic reference files, use symbolic links.
> Documentation/config.txt: expect HEAD to be a symbolic link.
> Documentation/core-tutorial.txt: This is similar to a symbolic link and points at
> Documentation/git-local-fetch.txt: Instead of regular file-to-file copying use symbolic links to the objects
> Documentation/git-symbolic-ref.txt:In the past, `.git/HEAD` was a symbolic link pointing at
> Documentation/git-symbolic-ref.txt:advertised (horrors). Therefore symbolic links are now deprecated
> Documentation/git-update-ref.txt:these symbolic pointers, whether they are symlinks or these
> Documentation/git-update-ref.txt:"regular file symbolic refs". It follows *real* symlinks only
> Documentation/glossary.txt: references are manipulated with the gitlink:git-symbolic-ref[1]
> Documentation/repository-layout.txt: a symbolic link instead of a symref that points at the current
These are all about how Git stores refs, and how HEAD used to be a symbolic link but has since changed to a symbolic reference... So less useful to what he was looking for I think.
--
Shawn.
