From: Eric Wong <eric@petta-tech.com>
To: Benoit SIGOURE <tsuna@lrde.epita.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Proposal for git-svn
Date: Wed, 18 Jul 2007 21:22:55 -0700 [thread overview]
Message-ID: <20070719042255.GA17433@muzzle> (raw)
In-Reply-To: <FAFA899D-EC45-4313-98ED-2D0A3FF37669@lrde.epita.fr>
Benoit SIGOURE <tsuna@lrde.epita.fr> wrote:
> Hello,
>
> I'm importing many SVN repositories in Git and I ran across a problem:
> ufloat.h has mode 120000but is not a link
>
> I've read the code and checked-out the revision where the problem
> occured and it turns out that some stupid user commited a broken
> symlink and I think that's where the problem came from. I'm
> proposing the following trivial change to let git-svn clone continue
> its work:
>
> diff --git a/git-svn.perl b/git-svn.perl
> index 01c3904..a82baf4 100755
> --- a/git-svn.perl
> +++ b/git-svn.perl
> @@ -2555,8 +2555,8 @@ sub close_file {
> sysseek($fh, 0, 0) or croak $!;
> if ($fb->{mode_b} == 120000) {
> sysread($fh, my $buf, 5) == 5 or croak $!;
> - $buf eq 'link ' or die "$path has mode 120000",
> - "but is not a link\n";
> + $buf eq 'link ' or warn "$path has mode 120000",
> + " but is not a link\n";
> }
> defined(my $pid = open my $out,'-|') or die "Can't
> fork: $!\n";
> if (!$pid) {
>
> (I also added a whitespace because "120000but" does not look good :D)
> I checked out the problematic revision in git and I see the broken
> symlink just like in SVN so I assume this change is correct.
Very strange. Since $buf didn't have the string "link " in it, did it
have a path name in it? If so, the sysread() would've advanced the $fh
offset by 5 bytes; causing an even more broken symlink to be added by git.
Would the following be more correct?
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -2552,9 +2552,15 @@ sub close_file {
}
sysseek($fh, 0, 0) or croak $!;
if ($fb->{mode_b} == 120000) {
- sysread($fh, my $buf, 5) == 5 or croak $!;
- $buf eq 'link ' or die "$path has mode 120000",
- "but is not a link\n";
+ eval {
+ sysread($fh, my $buf, 5) == 5 or croak $!;
+ $buf eq 'link ' or die "$path has mode 120000",
+ " but is not a link";
+ };
+ if ($@) {
+ warn "$@\n";
+ sysseek($fh, 0, 0) or croak $!;
+ }
}
defined(my $pid = open my $out,'-|') or die "Can't fork: $!\n";
if (!$pid) {
--
Eric Wong
next prev parent reply other threads:[~2007-07-19 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 21:07 [PATCH] Proposal for git-svn Benoit SIGOURE
2007-07-19 4:22 ` Eric Wong [this message]
2007-07-19 17:41 ` Benoit SIGOURE
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=20070719042255.GA17433@muzzle \
--to=eric@petta-tech.com \
--cc=git@vger.kernel.org \
--cc=tsuna@lrde.epita.fr \
/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).