From: David Aguilar <davvid@gmail.com>
To: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH v2 1/2] Ensure consistent usage of mergetool.keepBackup in git
Date: Fri, 10 Apr 2009 00:43:29 -0700 [thread overview]
Message-ID: <20090410074327.GA9369@gmail.com> (raw)
In-Reply-To: <49DEEE22.5030500@pelagic.nl>
On 0, "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl> wrote:
> David Aguilar wrote:
>
> I patched it this way because contrib/completion/git-completion.bash and
> Documentation/config.txt talk about mergetool.keepBackup while only
> contrib/difftool/git-difftool.txt talks about merge.keepBackup. That
> seemed the most logical way of doing it.
>
> I agree that some users might be surprised after this patch, otoh: I was
> quite surprised that I still had turds even when I set
> mergetool.keepBackup, which is what the documentation told me to do :-)
> Do we really want to keep using 2 names for the same thing?
>
> [rebasing now...]
>
> I'm seeing the following grep on pu:
>
> contrib/completion/git-completion.bash: mergetool.keepBackup
> Documentation/config.txt:mergetool.keepBackup::
> git-gui/lib/mergetool.tcl:if {[is_config_true merge.keepbackup]} {
> git-gui/git-gui:set default_config(merge.keepbackup) true
> git-gui/git-gui.sh:set default_config(merge.keepbackup) true
> git-mergetool.sh:merge_keep_backup="$(git config --bool merge.keepBackup
> || echo true)"
>
> So it seems that merge.keepBackup is actually used consistently in the
> code while the completion and documentation talk about mergetool.keepBackup.
>
> Shall I just patch the completion and documentation instead?
Oh wow thanks for your investigation.
It /seems/ like the docs and completion should be updated.
That's funny.. I guess it's so subtle it just passed by
unnoticed this whole time.
--
David
next prev parent reply other threads:[~2009-04-10 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 15:33 [[PATCH 1/1] Ensure consistent usage of mergetool.keepBackup Ferry Huberts
2009-04-09 15:30 ` RESEND [PATCH " Shawn O. Pearce
2009-04-09 15:45 ` [PATCH v2 1/2] Ensure consistent usage of mergetool.keepBackup in git Ferry Huberts
2009-04-10 3:27 ` David Aguilar
2009-04-10 6:58 ` Ferry Huberts (Pelagic)
2009-04-10 7:43 ` David Aguilar [this message]
2009-04-10 8:18 ` David Aguilar
2009-04-10 8:25 ` Ferry Huberts (Pelagic)
2009-04-10 14:48 ` Markus Heidelberg
2009-04-11 12:04 ` Charles Bailey
2009-04-09 15:45 ` [PATCH v2 2/2] Ensure consistent usage of mergetool.keepBackup in git-gui Ferry Huberts
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=20090410074327.GA9369@gmail.com \
--to=davvid@gmail.com \
--cc=ferry.huberts@pelagic.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.