From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Patrick.Higgins@cexp.com" <Patrick.Higgins@cexp.com>
Cc: git@vger.kernel.org
Subject: Re: Windows symlinks
Date: Tue, 24 Jun 2008 19:18:07 -0400 [thread overview]
Message-ID: <32541b130806241618p69f6167dycb09cdec1af8ba0@mail.gmail.com> (raw)
In-Reply-To: <911589C97062424796D53B625CEC0025E4618F@USCOBRMFA-SE-70.northamerica.cexp.com>
On 6/24/08, Patrick.Higgins@cexp.com <Patrick.Higgins@cexp.com> wrote:
> Cygwin's clever symlink trick seems to work pretty well in practice. I'm not exactly sure what
> it's doing, but it seems to create a shortcut that it's own programs understand. Some other
> non-Cygwin programs seem to understand them, too, but Java does not which is a big
> problem for me.
It seems somewhat odd that your developers are relying on an operating
system feature that doesn't even exist. I might suggest one of:
- add an abstraction layer to your Java applet that understands
cygwin-style symlinks
- actually just check in the file multiple times; git will store it
efficiently anyway
- improve your Makefile to automatically copy the files and/or create
symlinks at build time rather than storing the symlinks in revision
control.
My understanding of Clearcase is that it actually loads a virtual
filesystem driver in Windows and does all kinds of insane magic -
slowly and inefficiently, too - behind the scenes. Something tells me
git (and every other VCS :)) really doesn't want to go there.
Have fun,
Avery
next prev parent reply other threads:[~2008-06-24 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 22:42 Windows symlinks Patrick.Higgins
2008-06-24 23:18 ` Avery Pennarun [this message]
2008-06-26 3:50 ` Jay Soffian
2008-06-24 23:28 ` Jakub Narebski
2008-06-24 23:42 ` Patrick.Higgins
2008-06-25 0:04 ` Avery Pennarun
2008-06-25 17:50 ` Patrick.Higgins
2008-06-26 6:33 ` Andreas Ericsson
2008-06-24 23:29 ` Robin Rosenberg
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=32541b130806241618p69f6167dycb09cdec1af8ba0@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=Patrick.Higgins@cexp.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.
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).