From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Matt Seitz (matseitz)" <matseitz@cisco.com>
Cc: git@vger.kernel.org
Subject: Re: Symbolic link documentation
Date: Thu, 20 Sep 2007 18:20:02 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709201819340.28395@racer.site> (raw)
In-Reply-To: <70952A932255A2489522275A628B97C3052E98EB@xmb-sjc-233.amer.cisco.com>
Hi,
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;
Documentation/config.txt: If false, symbolic links are checked out as small plain files that
Documentation/config.txt: symbolic links. True by default.
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-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/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
Documentation/technical/racy-git.txt:files vs symbolic links) and executable bits (only for regular
Hth,
Dscho
next prev parent reply other threads:[~2007-09-20 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 17:17 Symbolic link documentation Matt Seitz (matseitz)
2007-09-20 17:20 ` Johannes Schindelin [this message]
2007-09-20 17:27 ` Shawn O. Pearce
2007-09-20 17:52 ` Matt Seitz (matseitz)
2007-09-20 18:11 ` Shawn O. Pearce
2007-09-20 19:11 ` Matt Seitz (matseitz)
2007-09-20 19:16 ` Shawn O. Pearce
2007-09-20 17:52 ` Johannes Schindelin
2007-09-20 18:50 ` Matt Seitz
2007-09-20 17:25 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0709201819340.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=matseitz@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).