From: Junio C Hamano <junkio@cox.net>
To: Alexander Klink <ak-git@cynops.de>
Cc: git@vger.kernel.org
Subject: Re: git-svn failure when symlink added in svn
Date: Sat, 28 Apr 2007 10:31:28 -0700 [thread overview]
Message-ID: <7virbgjthr.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <loom.20070428T144858-521@post.gmane.org> (Alexander Klink's message of "Sat, 28 Apr 2007 13:02:01 +0000 (UTC)")
Is it really the redirection that is the problem?
The process seeks $fh back to the beginning, reads 5 bytes from
it (to ensure that is 'link '), and then forks to feed $fh to
git-hash-object.
Now what do you really want to hash here? I do not know what
this "file that begins with 'link '" magic is about, but I
suspect that the child may or may not start reading from byte
offset 5 of that file, depending on how the low-level I/O is
tied to Perl.
Here is a little test script to imitate what the part in
close_file sub is doing. What does it output on MacOS (or
whatever systems that are having the same problem)?
On a Linux box, it appears that it reads the remainder of the
file and the test script says "child says: >>12345", so I am
assuming that is what close_file sub wants to do. If my
suspicion is correct, you would get "child says: >>link 12345",
in which case sysseek() commented out below would help,
perhaps.
-- >8 --
#!/usr/bin/perl -w
open F, ">footest";
print F "link 12345\n";
close F;
my ($fh, $buf, $n, $pid, $out);
open $fh, "<footest";
seek($fh, 0, 0);
$n = read($fh, $buf, 5);
print "read[$n]: $buf\n";
$pid = open $out , '-|';
if (!$pid) {
my $at = tell $fh;
print "child: at $at\n";
# We may want to do
#
# sysseek($fh, 5, 0);
#
# here.
open STDIN, '<&', $fh;
exec qw(sed -e s/^/>>/);
}
while (my $read = <$out>) {
print "child says: $read";
}
close ($out);
close ($fh);
next prev parent reply other threads:[~2007-04-28 17:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 6:41 git-svn failure when symlink added in svn Seth Falcon
2007-04-14 20:10 ` Eric Wong
2007-04-16 3:13 ` Seth Falcon
2007-04-26 23:07 ` Alexander Klink
2007-04-27 18:03 ` Linus Torvalds
2007-04-28 13:02 ` Alexander Klink
2007-04-28 16:54 ` Seth Falcon
2007-04-28 17:31 ` Junio C Hamano [this message]
2007-04-28 18:13 ` Seth Falcon
2007-04-28 18:34 ` Junio C Hamano
2007-04-28 21:15 ` Seth Falcon
2007-04-28 22:43 ` Junio C Hamano
[not found] ` <m2irbfqlze.fsf@ziti.local>
2007-04-29 18:26 ` Eric Wong
2007-04-30 14:43 ` Seth Falcon
2007-04-30 15:43 ` Eric Wong
2007-05-01 17:49 ` Seth Falcon
2007-04-29 18:31 ` Eric Wong
2007-04-29 21:01 ` Junio C Hamano
2007-04-29 22:21 ` Eric Wong
2007-04-30 0:24 ` Alexander Klink
2007-04-30 5:08 ` Junio C Hamano
2007-04-30 6:31 ` Eric Wong
2007-04-30 14:33 ` Seth Falcon
2007-05-01 20:53 ` Alexander Klink
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=7virbgjthr.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=ak-git@cynops.de \
--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).