From: Pavel Roskin <proski@gnu.org>
To: Petr Baudis <pasky@suse.cz>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Quick merge status updates.
Date: Sat, 08 Jul 2006 03:36:08 -0400 [thread overview]
Message-ID: <1152344168.26627.10.camel@dv> (raw)
In-Reply-To: <20060702204906.GG29115@pasky.or.cz>
On Sun, 2006-07-02 at 22:49 +0200, Petr Baudis wrote:
> Dear diary, on Wed, Jun 28, 2006 at 12:05:03PM CEST, I got a letter
> where Pavel Roskin <proski@gnu.org> said that...
> I feel that it is time for another stupid question of mine - why can't
> you just use lib?
>
> use lib ('@@INSTLIBDIR@@');
>
> Looks a lot better than some @INC unshifting, and it should be
> equivalent.
I honestly have no idea. I think whatever gets you closer to the
satisfaction of the "three conditions" should be used.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-07-08 7:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 0:23 Quick merge status updates Junio C Hamano
2006-06-28 5:04 ` Pavel Roskin
2006-06-28 8:49 ` Junio C Hamano
2006-06-28 10:05 ` Pavel Roskin
2006-06-28 10:14 ` Junio C Hamano
2006-07-02 20:49 ` Petr Baudis
2006-07-02 21:33 ` Junio C Hamano
2006-07-02 21:49 ` Petr Baudis
2006-07-02 22:50 ` Junio C Hamano
2006-07-02 23:49 ` Junio C Hamano
2006-07-03 0:00 ` Linus Torvalds
2006-07-03 0:06 ` Junio C Hamano
2006-07-03 20:29 ` Petr Baudis
2006-07-03 21:16 ` [PATCH] Use $GITPERLLIB instead of $RUNNING_GIT_TESTS and centralize @INC munging Petr Baudis
2006-07-08 7:36 ` Pavel Roskin [this message]
2006-06-28 7:32 ` Quick merge status updates Johannes Schindelin
2006-06-28 7:39 ` Johannes Schindelin
2006-06-28 8:51 ` Junio C Hamano
2006-06-28 9:13 ` Johannes Schindelin
2006-07-01 23:48 ` [PATCH] Git.pm: Avoid ppport.h Petr Baudis
2006-07-02 9:52 ` Johannes Schindelin
2006-07-02 19:05 ` Junio C Hamano
2006-07-02 20:57 ` [PATCH] Git.pm: Don't #define around die Petr Baudis
-- strict thread matches above, loose matches on Subject: below --
2006-07-02 21:40 Making perl scripts include the correct Git.pm Petr Baudis
2006-07-03 0:02 ` Junio C Hamano
2006-07-03 1:38 ` Junio C Hamano
2006-07-04 19:01 ` Marco Costalba
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=1152344168.26627.10.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.