From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Michael J Gruber <git@drmicha.warpmail.net>,
Jakub Narebski <jnareb@gmail.com>,
Johannes Sixt <j.sixt@viscovery.net>,
bill lam <cbill.lam@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>,
Paul Mackerras <paulus@samba.org>
Subject: [PATCH v4 4/4] Documentation: replace: talk a little bit about GIT_NO_REPLACE_OBJECTS
Date: Sun, 22 Nov 2009 07:56:44 +0100 [thread overview]
Message-ID: <20091122065645.4811.8117.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20091122064652.4811.38993.chriscool@tuxfamily.org>
It may be useful to know that this environment variable can be used
to prevent commands from using replacement refs.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
Documentation/git-replace.txt | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-replace.txt b/Documentation/git-replace.txt
index 69f704f..65a0da5 100644
--- a/Documentation/git-replace.txt
+++ b/Documentation/git-replace.txt
@@ -44,6 +44,9 @@ $ git cat-file commit foo
shows information about commit 'bar'.
+The 'GIT_NO_REPLACE_OBJECTS' environment variable can be set to
+achieve the same effect as the `--no-replace-objects` option.
+
OPTIONS
-------
-f::
--
1.6.5.1.gaf97d
prev parent reply other threads:[~2009-11-22 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 6:56 [PATCH v4 0/4] add new GIT_NO_REPLACE_OBJECTS env variable Christian Couder
2009-11-22 6:56 ` [PATCH v4 1/4] Documentation: fix typos and spelling in git-replace documentation Christian Couder
2009-11-22 6:56 ` [PATCH v4 2/4] replace: use a GIT_NO_REPLACE_OBJECTS env variable Christian Couder
2009-11-22 6:56 ` [PATCH v4 3/4] gitk: add "--no-replace-objects" option Christian Couder
2009-11-22 6:56 ` Christian Couder [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=20091122065645.4811.8117.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=cbill.lam@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=jnareb@gmail.com \
--cc=paulus@samba.org \
--cc=schwab@linux-m68k.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