As far as I know, there is no way git can tell the difference between a
hard link to a file (or should I say inode?) and the "original". I'm not
even sure there is a way to tell which one is which (maybe some raw
dumping of the file system's binary data?).
This way or another, hard links are not allowed for directories on a
system that wants to stay sane. So this doesn't help much.
Thanks anyhow. :)
On 06/09/2012 09:33 AM, Tomer Cohen wrote:
On Fri, Jun 8, 2012 at 12:24 PM, Eli Billauer <[email protected]
<mailto:[email protected]>> wrote:
I tried to symlink /boot/grub/ and got one single file (the
symbolic link itself). Some googling immediately revealed that
making git follow symlinks is a popular question, with a typical
answer that git doesn't like to do that (or can't do that).
Even if you're right, there is no reason why git won't follow hardlinks.
--
Tomer Cohen
http://tomercohen.com
--
Web: http://www.billauer.co.il
_______________________________________________
Linux-il mailing list
[email protected]
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
