git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "martin f. krafft" <madduck@madduck.net>
Subject: Re: [PATCH] Install man3 manpages to $PREFIX/share/man/man3 even  for site installs
Date: Thu, 19 Jul 2007 17:46:00 -0700	[thread overview]
Message-ID: <861wf37vhz.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <7vzm1r29df.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Thu, 19 Jul 2007 17:42:52 -0700")

>>>>> "Junio" == Junio C Hamano <gitster@pobox.com> writes:

Junio> Randal, I cannot decide if this is the right thing to do, or 
Junio> better than what we currently do.  Could you care to enlighten
Junio> us please?

I'll have to research it.  On *every single* major release of Perl, and even
some of the minor ones, the rules for what Makefile.PL does have changed.
It's really maddening.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

  reply	other threads:[~2007-07-20  0:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 12:45 [PATCH] Install man3 manpages to $PREFIX/share/man/man3 even for site installs martin f. krafft
2007-07-20  0:42 ` Junio C Hamano
2007-07-20  0:46   ` Randal L. Schwartz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-20  7:23 Install section 3 manpages to .../share/man for consistency martin f. krafft
2007-08-20  7:23 ` [PATCH] Install man3 manpages to $PREFIX/share/man/man3 even for site installs martin f. krafft
2007-08-23  8:11   ` Junio C Hamano

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=861wf37vhz.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=madduck@madduck.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).