git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Document GIT_SSH environment variable alongside other variables
Date: Mon, 6 Aug 2007 00:16:40 +0200	[thread overview]
Message-ID: <200708060016.40829.jnareb@gmail.com> (raw)
In-Reply-To: <20070804060652.GA28379@spearce.org>

Shawn O. Pearce wrote:

> The GIT_SSH environment variable has survived for quite a while
> without being documented, but has been mentioned on list and on
> my day-job repositories can only be accessed via magic supplied
> through the wonderous hack that is GIT_SSH.

Thanks a lot.

By the way, I plan on documenting existing environmental variables used 
by git better (for after 1.5.3). First, separate "Environmental 
variables" section in Documentation/git.txt into separate file (similar 
to the config.txt file), named environment.txt. Second, add to the list 
of variables links to variables which are documented in other manpages, 
similarly to how for example GIT_AUTHOR_NAME etc. are described. Then 
add one by one environmental variables which are not documented at all: 
GIT_SSH_PUSH/GIT_SSH_PULL, GIT_CURL_VERBOSITY, GIT_REFLOG_ACTION, 
GIT_GRAFT_FILE and GIT_TEMPLATE_DIR.

-- 
Jakub Narebski
Poland

      reply	other threads:[~2007-08-05 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-04  6:06 [PATCH] Document GIT_SSH environment variable alongside other variables Shawn O. Pearce
2007-08-05 22:16 ` Jakub Narebski [this message]

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=200708060016.40829.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=spearce@spearce.org \
    /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).