From: Jakub Narebski <jnareb@gmail.com>
To: Seth Kriticos <seth.kriticos@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: How does git deal with hard links in source code?
Date: Mon, 23 Aug 2010 02:00:56 -0700 (PDT) [thread overview]
Message-ID: <m3fwy5og9p.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTik3858Kf6MSPALeNYrE6L=ixf=0s028+_ie_SW_@mail.gmail.com>
Seth Kriticos <seth.kriticos@googlemail.com> writes:
> I've got a question my google-fu and the docs were not able
> to answer:
>
> Is there a way to preserve the hard links that are within
> a git repository checkout (the stuff that is tracked by the
> git repository)?
No, there isn't, and there shouldn't. Not all filesystems support
hardlinks.
> The use-case I have is the following: I want to have two
> different template directories for stuff in the tracked
> sources: a base one and some extended ones. I want to have
> the stuff from the base one hard-linked to the extended one,
> so changes in the base one change all the other depending
> templates too.
>
> Now for testing I committed and pushed an instance of this
> and then cloned the repository, and it ate my hard links
> (checked out two separate copies of the files).
>
> Is there a way to convince git not to eat my hard links
> without some complicated scripting magic and checkout hooks?
Make hardlinks on deploy.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2010-08-23 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 8:33 How does git deal with hard links in source code? Seth Kriticos
2010-08-23 9:00 ` Jakub Narebski [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fwy5og9p.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=seth.kriticos@googlemail.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.
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 NNTP newsgroup(s).