From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Eliminate Scalar::Util usage from private-Error.pm
Date: Wed, 26 Jul 2006 04:10:58 +0200 [thread overview]
Message-ID: <20060726021058.GV13776@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.63.0607260356480.29667@wbgn013.biozentrum.uni-wuerzburg.de>
Hi,
Dear diary, on Wed, Jul 26, 2006 at 04:01:03AM CEST, I got a letter
where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...
> After a lot of fiddling, it works here. Remarks:
thanks for the testing!
> - It is not at all easy to run git (Perl scripts) in-place. At least for
> Python, you can set a variable in config.mak and be done with it.
Does setting prefix to the same directory as where your Git tree is
help? (If so, we might want to document it.)
> - private_Error.pm is not used. I had to rename it for Error.pm to be
> picked up.
Hmm, yes, I guess it is copied in place only during the installation.
We might add something like
all:
cp private-Error.pm blib/lib/Error.pm
to the perl/Makefile. Opinions?
> - It even passes t7001 now. _After_ I spent two hours rewriting it in C.
Thanks for the patience - I hope we will finally get all the remaining
Perl problems sorted out.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
next prev parent reply other threads:[~2006-07-26 2:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 11:57 [PATCH] cvsserver: avoid warning about active db handles Johannes Schindelin
2006-07-25 12:07 ` Martin Langhoff (CatalystIT)
2006-07-25 14:53 ` Johannes Schindelin
2006-07-25 15:52 ` Petr Baudis
2006-07-25 16:10 ` Git.xs problem, was " Johannes Schindelin
2006-07-26 1:03 ` [PATCH] Eliminate Scalar::Util usage from private-Error.pm Petr Baudis
2006-07-26 2:01 ` Johannes Schindelin
2006-07-26 2:03 ` Johannes Schindelin
2006-07-26 2:11 ` Petr Baudis
2006-07-26 2:26 ` Johannes Schindelin
2006-07-26 2:10 ` Petr Baudis [this message]
2006-07-26 2:25 ` Johannes Schindelin
2006-07-26 13:35 ` Jakub Narebski
2006-07-26 15:17 ` Johannes Schindelin
2006-07-26 17:59 ` Luben Tuikov
2006-07-27 12:47 ` Randal L. Schwartz
2006-07-27 14:00 ` Johannes Schindelin
2006-07-27 14:22 ` Randal L. Schwartz
2006-07-27 14:32 ` Johannes Schindelin
2006-07-26 21:34 ` Petr Baudis
[not found] ` <7vhd15cfaj.fsf@assigned-by-dhcp.cox.net>
2006-07-26 2:15 ` Petr Baudis
-- strict thread matches above, loose matches on Subject: below --
2006-07-10 13:00 Perl gurus: why do we need Scalar::Util? Petr Baudis
2006-07-11 0:53 ` [PATCH] Eliminate Scalar::Util usage from private-Error.pm Petr Baudis
2006-07-11 1:38 ` Randal L. Schwartz
2006-07-11 1:40 ` Randal L. Schwartz
2006-07-11 1:42 ` Randal L. Schwartz
2006-07-11 1:57 ` Junio C Hamano
2006-07-11 3:38 ` Randal L. Schwartz
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060726021058.GV13776@pasky.or.cz \
--to=pasky@suse.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).