All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: "Matthieu Beauchamp" <matthieu.beauchamp.boulay@gmail.com>,
	"Torsten Bögershausen" <tboegi@web.de>
Cc: Matthieu Beauchamp-Boulay via GitGitGadget
	<gitgitgadget@gmail.com>,
	git@vger.kernel.org, Matheus Tavares <matheus.tavb@gmail.com>,
	Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] ignores: handle non UTF-8 exclude files
Date: Wed, 7 Jan 2026 14:36:19 +0000	[thread overview]
Message-ID: <072dc5ef-e750-4023-bf6c-30b4b143beca@gmail.com> (raw)
In-Reply-To: <CALH9GrYi0dYo4LJg8ww1cDOETiOT44m0zQgkxLsxqEuMmv_myQ@mail.gmail.com>

On 06/01/2026 20:32, Matthieu Beauchamp wrote:
> 
> Yes you are correct, but I want to address the issues for users who may not
> realize that they used the wrong encoding when creating their exclude file.
> For that case I don't see how the fact that powershell can be configured to
> UTF-8 helps, aside from preventing repeating the same mistake.

My concern with that is that it ends up hampering collaboration with 
people using bash on Windows or a native shell on other platforms. If 
they append to a UTF-16 encoded .gitignore with "echo path >>.gitignore" 
you'll end up with a mix of encodings in the same file. Similarly if you 
use powershell to append to an existing file that is UTF-8 encoded with 
"echo hello >>.gitignore" is the appended text UTF-16 encoded resulting 
in mixed encodings in the same file?

Thanks

Phillip


  reply	other threads:[~2026-01-07 14:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-03 22:16 [PATCH] ignores: handle non UTF-8 exclude files Matthieu Beauchamp-Boulay via GitGitGadget
2026-01-04  2:54 ` Junio C Hamano
2026-01-06 19:52   ` Matthieu Beauchamp
2026-01-04 17:35 ` Torsten Bögershausen
2026-01-06 20:32   ` Matthieu Beauchamp
2026-01-07 14:36     ` Phillip Wood [this message]
2026-01-04 19:40 ` brian m. carlson
2026-01-06 20:45   ` Matthieu Beauchamp
2026-01-06 23:22     ` brian m. carlson
2026-01-07  1:35       ` Collin Funk
2026-01-07 14:28         ` Phillip Wood
2026-01-07 23:38         ` brian m. carlson
2026-01-08  1:13           ` Collin Funk

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=072dc5ef-e750-4023-bf6c-30b4b143beca@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=matheus.tavb@gmail.com \
    --cc=matthieu.beauchamp.boulay@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=tboegi@web.de \
    /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.