From: "Sverre Johansen" <sverre.johansen@gmail.com>
To: git@vger.kernel.org
Subject: git-svn fix for broken symlinks
Date: Tue, 18 Dec 2007 17:11:56 +0100 [thread overview]
Message-ID: <a74c0d680712180811m216699a4h7123039c3158c2ed@mail.gmail.com> (raw)
Hi,
There is a bug in older versions of SVN that makes it possible to create
symlinks where the target is not the path to the file, but instead the
content of the target file. The bug is described here [0].
This breaks git-svn because it expects files which is marked as symlinks
to have the content "link: <filename>".
There was a thread about this back in July, resulting in this patch [1]. Is that
patch planned to be merged anytime soon? I'm using it, and it works great
for me.
[0]: http://subversion.tigris.org/issues/show_bug.cgi?id=2692
[1]: http://kerneltrap.org/mailarchive/git/2007/7/19/252025
--
Sverre Johansen
next reply other threads:[~2007-12-18 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 16:11 Sverre Johansen [this message]
2007-12-19 8:48 ` git-svn fix for broken symlinks Eric Wong
2007-12-19 9:37 ` Junio C Hamano
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=a74c0d680712180811m216699a4h7123039c3158c2ed@mail.gmail.com \
--to=sverre.johansen@gmail.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).