From: Eric Wong <normalperson@yhbt.net>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: latest update to git-svn blows up for me
Date: Sun, 3 Dec 2006 23:00:21 -0800 [thread overview]
Message-ID: <20061204070021.GG1369@localdomain> (raw)
In-Reply-To: <863b7wnwcw.fsf@blue.stonehenge.com>
"Randal L. Schwartz" <merlyn@stonehenge.com> wrote:
>
> Does this ring a bell?
Nope.
> Fetching git-svn
> M trunk/lib/Perl/Critic/Policy/TestingAndDebugging/MisplacedShebang.pm
> M trunk/lib/Perl/Critic/Policy/TestingAndDebugging/ProhibitShebangWarningsArg.pm
> M trunk/lib/Perl/Critic/Policy/TestingAndDebugging/RequirePortableShebang.pm
> M trunk/compilers/past-pm/POST/Compiler.pir
> M trunk/compilers/past-pm/PAST/Compiler.pir
> M trunk/compilers/past-pm/PAST-pm.pir
> M trunk/languages/perl6/src/quote.pir
> M trunk/languages/perl6/src/classes/Str.pir
> M trunk/languages/perl6/src/classes/Code.pir
> M trunk/languages/perl6/src/classes/Num.pir
> M trunk/languages/plumhead/t/selection.txt
> M trunk/languages/plumhead/t/superglobals.t
> M trunk/languages/plumhead/t/strings.t
> M trunk/languages/tcl/runtime/builtin/clock.pir
> no blob information
> 512 at /opt/git/bin/git-svn line 457
> main::fetch_lib() called at /opt/git/bin/git-svn line 328
> main::fetch() called at /opt/git/bin/git-svn line 973
> main::fetch_child_id('git-svn') called at /opt/git/bin/git-svn line 991
> main::rec_fetch('', '/Volumes/UFS/MIRROR/parrot-GITSVN/.git/svn') called at /opt/git/bin/git-svn line 747
> main::multi_fetch() called at /opt/git/bin/git-svn line 187
> 512 at /opt/git/bin/git-svn line 980
> main::fetch_child_id('git-svn') called at /opt/git/bin/git-svn line 991
> main::rec_fetch('', '/Volumes/UFS/MIRROR/parrot-GITSVN/.git/svn') called at /opt/git/bin/git-svn line 747
> main::multi_fetch() called at /opt/git/bin/git-svn line 187
This is on r15941 of https://svn.perl.org/parrot/trunk ? I can't seem
to reproduce this with git svn fetch -r15940:15941
--
next prev parent reply other threads:[~2006-12-04 7:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 4:00 latest update to git-svn blows up for me Randal L. Schwartz
2006-12-04 7:00 ` Eric Wong [this message]
2006-12-04 11:41 ` Randal L. Schwartz
2006-12-04 18:12 ` Eric Wong
2006-12-04 19:36 ` Randal L. Schwartz
2006-12-04 19:54 ` Eric Wong
2006-12-04 20:04 ` Randal L. Schwartz
2006-12-04 20:08 ` Eric Wong
2006-12-04 20:10 ` Randal L. Schwartz
2006-12-04 20:51 ` Eric Wong
2006-12-05 4:08 ` Eric Wong
2006-12-05 4:19 ` Randal L. Schwartz
2006-12-05 4:33 ` Randal L. Schwartz
2006-12-05 9:13 ` Eric Wong
2006-12-05 16:47 ` Linus Torvalds
2006-12-08 9:55 ` [PATCH] git-svn: extra error check to ensure we open a file correctly Eric Wong
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=20061204070021.GG1369@localdomain \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
/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).