Getting git to follow symlinks (again)

Somebody already asked how you can get git to follow symlinks. There was an answer for a symlinked directory, but not for a symlinked file. It was also over a year ago.

Question: how do you get git to follow a symlink and add the file it refers to?

  • Getting rid of “git: /usr/local/lib/ no version information available (required by git)”
  • Is it rude to commit design documents to github?
  • How do I import a local java library in clojure? (lein)
  • Nice Git architecture for server / client?
  • Cannot remove remote origin
  • merge one local branch into another local branch
  • Here is the old question: How can I get git to follow symlinks?. There’s also a question about what git typically does How does git handle symbolic links?. I’m after a way of changing this behaviour.

    In case you care: I’m running git on unix and git version 1.6.0 on mac.

  • Git - Remove commit from history
  • git clone from->to directory confusion
  • How do i restore my git repository after using git -r rm
  • Using maven-release-plugin with git-1.8.5
  • How can I push my existing Git repository to Team Foundation Service
  • How do you get git repos name in some git repository?
  • 4 Solutions collect form web for “Getting git to follow symlinks (again)”

    I’m pretty sure there’s no way.

    Additionally, it sounds like a kind of insecure, undefined behavior – what should it do when you move between versions of the file and it needs to write to it? In particular, if you check out a revision before it was added, do you really want it to remove the contents of a file outside the repository? What happens if you come back to present and recreate the file, or if the symlink itself is modified – should git also track the symlink itself?

    Things along these lines were said on the git mailing list late last year in response to essentially the same question.

    You can use hardlinks instead of softlinks (a.k.a. symlinks). Git will then see the contents of the linked file. The disadvantage is that when someone checks out, the file is created as a normal file in the checked-out directory, because Git does not understand it as a link.

    how about using hard links, then git has no idea its a linked file (does it?)

    The trouble with using hardlinks is that if something writing to the other location replaces the file, rather than just writing changes to it, then the destination file has a new inode on the filesystem and the hardlink no longer points to it, so the files are out of sync.

    Git Baby is a git and github fan, let's start git clone.