public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha•warpmail.net>
To: Christian Couder <chriscool@tuxfamily•org>
Cc: Junio C Hamano <gitster@pobox•com>,
	git@vger•kernel.org, 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: Re: [PATCH 1/2] replace: use a GIT_NO_REPLACE_OBJECTS env variable
Date: Tue, 17 Nov 2009 10:33:28 +0100	[thread overview]
Message-ID: <4B026DE8.9070905@drmicha.warpmail.net> (raw)
In-Reply-To: <20091117051125.3588.91072.chriscool@tuxfamily.org>

Christian Couder venit, vidit, dixit 17.11.2009 06:11:
> This environment variable is set when the --no-replace-objects
> flag is passed to git, and it is read when other environment
> variables are read.
> 
> It is useful for example for scripts, as the git commands used in
> them can now be aware that they must not read replace refs.
> 
> Signed-off-by: Christian Couder <chriscool@tuxfamily•org>

Tested-by: Michael J Gruber <git@drmicha•warpmail.net>

:) This works, thanks, as well as the gitk patch 2/2, which is difficult
to cover by test scripts. Some OSes (or rather certain setenv/putenv
variants) have problems distinguishing an unset variable from an empty
one. I think we've worked around this, but avoiding it is safer, as J6t
pointed out.

Thanks!
Michael

  parent reply	other threads:[~2009-11-17  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17  5:11 [PATCH 1/2] replace: use a GIT_NO_REPLACE_OBJECTS env variable Christian Couder
2009-11-17  7:42 ` Johannes Sixt
2009-11-18  6:48   ` Christian Couder
2009-11-17  9:33 ` Michael J Gruber [this message]
2009-11-18  6:49   ` Christian Couder

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=4B026DE8.9070905@drmicha.warpmail.net \
    --to=git@drmicha$(echo .)warpmail.net \
    --cc=cbill.lam@gmail$(echo .)com \
    --cc=chriscool@tuxfamily$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=j.sixt@viscovery$(echo .)net \
    --cc=jnareb@gmail$(echo .)com \
    --cc=paulus@samba$(echo .)org \
    --cc=schwab@linux-m68k$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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