From: "Joachim Schmitz" <jojo@schmitz-digital.de>
To: git@vger.kernel.org
Subject: Re: [PATCH 0/8] fix git-config with duplicate variable entries
Date: Fri, 23 Nov 2012 11:37:51 +0100 [thread overview]
Message-ID: <k8njm8$b1l$1@ger.gmane.org> (raw)
In-Reply-To: 7vehjm20yu.fsf@alter.siamese.dyndns.org
Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
...
> Not exactly. There are three classes of people:
>
> - wrote scripts using --get; found out that --get barfs if you feed
> two or more of the same, and have long learned to accept it as a
> limitation and adjusted their configuration files to avoid it.
> They have been doing just fine and wouldn't benefit from this
> series at all.
>
> - wrote scripts using --get, relying on it barfing if fed zero
> (i.e. missing) or two or more (i.e. ambiguous), perhaps a way to
> keep their configuration files (arguably unnecessarily) clean.
> They are directly harmed by this series.
>
> - wrote scripts using --get-all and did the last-one-wins
> themselves. They wouldn't benefit directly from this series,
> unless they are willing to spend a bit of time to remove their
> own last-one-wins logic and replace --get-all with --get (but the
> same effort is needed to migrate to --get-one).
>
> - wanted to write scripts using --get, but after finding out that
> it barfs if you feed two, gave up emulating the internal, without
> realizing that they could do so with --get-all. They can now
> write their scripts without using --get-all.
There are three classes ofpeople: those that can count and those that can't
Sorry could not resist ;-)
next prev parent reply other threads:[~2012-11-23 10:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 15:55 The config include mechanism doesn't allow for overwriting Ævar Arnfjörð Bjarmason
2012-10-22 21:15 ` Jeff King
2012-10-23 14:13 ` Ævar Arnfjörð Bjarmason
2012-10-23 22:35 ` [PATCH 0/8] fix git-config with duplicate variable entries Jeff King
2012-10-23 22:35 ` [PATCH 1/8] t1300: style updates Jeff King
2012-10-24 6:33 ` Johannes Sixt
2012-10-24 6:37 ` Jeff King
2012-10-24 7:07 ` [PATCHv2 " Jeff King
2012-10-23 22:36 ` [PATCH 2/8] t1300: remove redundant test Jeff King
2012-10-23 22:36 ` [PATCH 3/8] t1300: test "git config --get-all" more thoroughly Jeff King
2012-10-23 22:36 ` [PATCH 4/8] git-config: remove memory leak of key regexp Jeff King
2012-10-23 22:38 ` [PATCH 5/8] git-config: fix regexp memory leaks on error conditions Jeff King
2012-10-23 22:40 ` [PATCH 6/8] git-config: collect values instead of immediately printing Jeff King
2012-10-23 22:41 ` [PATCH 7/8] git-config: do not complain about duplicate entries Jeff King
2012-10-23 22:41 ` [PATCH 8/8] git-config: use git_config_with_options Jeff King
2012-10-24 6:33 ` Johannes Sixt
2012-10-24 19:14 ` Ævar Arnfjörð Bjarmason
2012-11-20 19:08 ` [PATCH 0/8] fix git-config with duplicate variable entries Junio C Hamano
2012-11-21 19:27 ` Jeff King
2012-11-21 19:46 ` Junio C Hamano
2012-11-21 20:06 ` Jeff King
2012-11-21 20:42 ` Junio C Hamano
2012-11-23 10:37 ` Joachim Schmitz [this message]
2012-10-24 0:46 ` The config include mechanism doesn't allow for overwriting John Szakmeister
2012-10-24 0:51 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='k8njm8$b1l$1@ger.gmane.org' \
--to=jojo@schmitz-digital.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).