All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Scott R Parish <sRp@srparish.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] allow git to use the PATH for finding subcommands and help   docs
Date: Fri, 19 Oct 2007 09:33:03 +0200	[thread overview]
Message-ID: <47185DAF.7060809@viscovery.net> (raw)
In-Reply-To: <20071019065931.GB1463@srparish.net>

Scott R Parish schrieb:
>  + check PATH for git_exec_path after other locations but before builtin
>  + prepend MANPATH and PERL5LIB in addition to PATH

This says *what* the patch does, but not *why*. Care to explain?

And then your explanation should go into the commit message.

-- Hannes

  reply	other threads:[~2007-10-19  8:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  6:59 [PATCH] allow git to use the PATH for finding subcommands and help docs Scott R Parish
2007-10-19  7:33 ` Johannes Sixt [this message]
2007-10-19 13:04   ` Scott Parish
2007-10-19 13:21     ` Johannes Sixt
2007-10-19 14:18       ` Scott Parish
2007-10-19 14:34         ` Johannes Sixt
2007-10-19 14:27     ` Johannes Schindelin
2007-10-19 16:48       ` Mike Hommey
2007-10-19 17:19         ` Johannes Schindelin
2007-10-20  6:42       ` Scott Parish

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=47185DAF.7060809@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@vger.kernel.org \
    --cc=sRp@srparish.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.
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.