From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
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: Re: [PATCH v3] gitk: add --no-replace-objects option
Date: Fri, 20 Nov 2009 12:04:39 -0800 [thread overview]
Message-ID: <7vocmxvu7c.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20091120194046.4469.53971.chriscool@tuxfamily.org> (Christian Couder's message of "Fri\, 20 Nov 2009 20\:40\:45 +0100")
Christian Couder <chriscool@tuxfamily.org> writes:
> This option simply sets the GIT_NO_REPLACE_OBJECTS environment
> variable, and that is enough to make gitk ignore replace refs.
This is a much less interesting implementation detail than everything else
you should talk about the new feature you are adding; why is it the first
sentence of the message?
> The GIT_NO_REPLACE_OBJECTS is set to "1" instead of "" as it is
> safer on some platforms, thanks to Johannes Sixt and Michael J
> Gruber.
And this is even less interesting.
> Replace refs are useful to change some git objects after they
> have started to be shared between different repositories. One
> might want to ignore them to see the original state.
This is what the reader needs to see to understand why this patch is
worthy of consideration. It is a minor offense that the paragraph does
not end with "... original state, and --no-replace-objects option can be
used from the command line to do so", but this could be excused if this is
made the first paragraph in the message, close to the subject.
I wonder if this switch deserves run-time flippability, though...
> Tested-by: Michael J Gruber <git@drmicha.warpmail.net>
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
> gitk-git/gitk | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/gitk-git/gitk b/gitk-git/gitk
> index a0214b7..c586b93 100644
> --- a/gitk-git/gitk
> +++ b/gitk-git/gitk
> @@ -128,7 +128,7 @@ proc unmerged_files {files} {
> }
>
> proc parseviewargs {n arglist} {
> - global vdatemode vmergeonly vflags vdflags vrevs vfiltered vorigargs
> + global vdatemode vmergeonly vflags vdflags vrevs vfiltered vorigargs env
>
> set vdatemode($n) 0
> set vmergeonly($n) 0
> @@ -208,6 +208,9 @@ proc parseviewargs {n arglist} {
> # git rev-parse doesn't understand --merge
> lappend revargs --gitk-symmetric-diff-marker MERGE_HEAD...HEAD
> }
> + "--no-replace-objects" {
> + set env(GIT_NO_REPLACE_OBJECTS) "1"
> + }
> "-*" {
> # Other flag arguments including -<n>
> if {[string is digit -strict [string range $arg 1 end]]} {
> --
> 1.6.5.1.gaf97d
next prev parent reply other threads:[~2009-11-20 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 19:40 [PATCH v3] gitk: add --no-replace-objects option Christian Couder
2009-11-20 20:04 ` Junio C Hamano [this message]
2009-11-20 20:42 ` Christian Couder
2009-11-20 20:55 ` Junio C Hamano
2009-11-20 21:15 ` 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=7vocmxvu7c.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=cbill.lam@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--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