All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Steve Groeger <GROEGES@uk.ibm.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	git@vger.kernel.org
Subject: Re: Use of new .gitattributes working-tree-encoding attribute across different platform types
Date: Mon, 2 Jul 2018 14:20:16 -0400	[thread overview]
Message-ID: <20180702182016.GB12208@sigill.intra.peff.net> (raw)
In-Reply-To: <4621C69D-B837-43ED-8570-462D4CF2BBA0@gmail.com>

On Mon, Jul 02, 2018 at 04:09:32PM +0200, Lars Schneider wrote:

> Brian had a good argument [1] for an even more flexible system
> proposed by Peff:
> 
> 
> 1) We allow users to define custom encoding mappings in their Git config. 
> Example:
> 
>     git config --global core.encoding.myenc UTF-16

I think this should be encoding.myenc.something. In Git's config format,
only the subsection names (the middle of a three-dot name) are
unconstrained. So even if encoding.myenc only ever has one key
("replace" or "useInstead" or whatever you want to call it), there's
value in organizing the namespace that way.

And as a bonus, it leaves room for extending the feature later if we do
need more keys.

-Peff

  reply	other threads:[~2018-07-02 18:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27  7:54 Use of new .gitattributes working-tree-encoding attribute across different platform types Steve Groeger
2018-06-27 17:38 ` Torsten Bögershausen
2018-06-28  2:44 ` brian m. carlson
2018-06-28 14:34   ` Jeff King
2018-06-28 17:21     ` Lars Schneider
2018-06-28 17:27       ` Jeff King
2018-07-01 17:56         ` brian m. carlson
2018-07-02 18:17           ` Jeff King
2018-07-03 16:01             ` Junio C Hamano
2018-07-02 12:13     ` Steve Groeger
2018-07-02 14:09       ` Lars Schneider
2018-07-02 18:20         ` Jeff King [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-27  7:50 Steve Groeger

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=20180702182016.GB12208@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=GROEGES@uk.ibm.com \
    --cc=git@vger.kernel.org \
    --cc=larsxschneider@gmail.com \
    --cc=sandals@crustytoothpaste.net \
    /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.