From: Tait <git.git@t41t.com>
To: Git ML <git@vger.kernel.org>
Cc: Pierre Habouzit <madcoder@madism.org>
Subject: Re: fixing workdirs
Date: Thu, 8 Jul 2010 11:37:14 -0700 [thread overview]
Message-ID: <20100708183714.GR2480@ece.pdx.edu> (raw)
In-Reply-To: <20100708110842.GC12789@madism.org>
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>
On programs (like git) pretending to be cross-platform, symlinks should
be avoided. They are to varying degrees, painful on non-*nix operating
systems.
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.
next prev parent reply other threads:[~2010-07-08 18:48 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 [this message]
2010-07-08 18:56 ` Joshua Jensen
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=20100708183714.GR2480@ece.pdx.edu \
--to=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 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).