From: Seth Kriticos <seth.kriticos@googlemail.com>
To: git@vger.kernel.org
Subject: How does git deal with hard links in source code?
Date: Mon, 23 Aug 2010 10:33:38 +0200 [thread overview]
Message-ID: <AANLkTik3858Kf6MSPALeNYrE6L=ixf=0s028+_ie_SW_@mail.gmail.com> (raw)
Hi list,
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)?
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?
~ Seth Kriticos
next reply other threads:[~2010-08-23 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 8:33 Seth Kriticos [this message]
2010-08-23 9:00 ` How does git deal with hard links in source code? Jakub Narebski
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='AANLkTik3858Kf6MSPALeNYrE6L=ixf=0s028+_ie_SW_@mail.gmail.com' \
--to=seth.kriticos@googlemail.com \
--cc=git@vger.kernel.org \
/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).