From: Joshua Jensen <jjensen@workspacewhiz.com>
To: Tait <git.git@t41t.com>
Cc: Git ML <git@vger.kernel.org>, Pierre Habouzit <madcoder@madism.org>
Subject: Re: fixing workdirs
Date: Thu, 08 Jul 2010 12:56:15 -0600 [thread overview]
Message-ID: <4C361F4F.9070505@workspacewhiz.com> (raw)
In-Reply-To: <20100708183714.GR2480@ece.pdx.edu>
----- Original Message -----
From: Tait
Date: 7/8/2010 12:37 PM
> Pierre Habouzit<madcoder_madism.org> said (on 2010/07/08):
>> ... The workdir HEAD reflog is then a
>> symlink to the masters.
> #include<std-symlink-rant>
>
> Windows is an especially compatibility-breaking example, not only on the
> programming side, but also in relation to user interface, and compatibility
> with other programs. Programming-wise, documentation is sparse and
> would require lots of platform-specific work-arounds. The user-interface
> support is worse than terrible. And even if git does everything right,
> there's no guarantee a copy, backup/restore, antivirus program, etc. won't
> come along and corrupt the environment git so carefully created. Many of
> those other programs don't properly handle Windows reparse points. For
> those interested, http://shell-shocked.org/article.php?id=284 gives a
> reasonable-looking overview of the details on Windows.
I'm going to go out on a limb here and say that I suspect symbolic links
work fine in Windows Vista and 7, because they are used all over the
file system Microsoft installs. Symbolic links for files, in
particular, didn't exist until Vista.
Josh
next prev parent reply other threads:[~2010-07-08 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 11:08 fixing workdirs Pierre Habouzit
2010-07-08 18:37 ` Tait
2010-07-08 18:56 ` Joshua Jensen [this message]
2010-07-09 7:49 ` Pierre Habouzit
2010-07-08 19:40 ` Junio C Hamano
2010-07-08 19:56 ` Avery Pennarun
2010-07-09 7:56 ` Pierre Habouzit
2010-07-09 22:25 ` Junio C Hamano
2010-07-19 9:02 ` Pierre Habouzit
2010-08-17 18:34 ` Jan Hudec
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=4C361F4F.9070505@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--cc=git.git@t41t.com \
--cc=git@vger.kernel.org \
--cc=madcoder@madism.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.