git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH 0/3] C implementation of git, take two.
Date: Wed, 16 Nov 2005 00:40:20 +0100	[thread overview]
Message-ID: <437A71E4.9030604@op5.se> (raw)

The commit-messages says it all really, but in case anyone doesn't want 
to read near-identical code to find out what's different between take 
two and take one, I'll just list it briefly here.

* Renamed "git --lib" and $GIT_LIB to "git --exec-path" and 
$GIT_EXEC_PATH, respectively, as per Junio's decision.

* Implemented Linus' idea of prepending exec-path to $PATH.

* "git --help diff-index" brings up the git-diff-index(1) man-page 
(patch 3/3), as does "git --help git-diff-index".

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

                 reply	other threads:[~2005-11-15 23:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=437A71E4.9030604@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.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).