git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Justus Ranvier <justus@opentransactions.org>
Cc: Matheus Tavares <matheus.bernardino@usp.br>,
	Rene Kita <mail@rkta.de>, git <git@vger.kernel.org>
Subject: Re: gitignore as symbolic link
Date: Sat, 23 Oct 2021 12:01:49 +0000	[thread overview]
Message-ID: <YXP5rZT5IgFcMZs0@camp.crustytoothpaste.net> (raw)
In-Reply-To: <fa4b28b1-9b5e-0201-5afe-2e8f294fa9b4@opentransactions.org>

[-- Attachment #1: Type: text/plain, Size: 986 bytes --]

On 2021-10-22 at 23:55:16, Justus Ranvier wrote:
> Suppose a person is managing N repositories. Would that person prefer to
> maintain the list of files to ignore for every random IDE that anybody who
> joins the team might want to use in:
> 
> a: One place
> b: N places

Developers should be responsible for ensuring that their own editor's
temporary files are ignored.  For example, I use Vim, so it's my
responsibility to ensure that I globally ignore swap files using
"core.excludesFile" or that my editor is configured not to produce them.
(In my case, it's the latter.)

As you point out, it's unsustainable to have to manage a list of the
detritus of every possible editor.  What if I had decided to use an
editor that is not very popular, like ae, joe, or acme?  Should every
project be responsible for dealing with my uncommon editor, or should I
be responsible for my own editing hygiene?
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2021-10-23 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  1:07 gitignore as symbolic link Justus Ranvier
2021-10-22 16:49 ` Rene Kita
2021-10-22 22:40   ` Matheus Tavares
2021-10-22 23:29     ` Justus Ranvier
2021-10-22 23:55     ` Justus Ranvier
2021-10-23 12:01       ` brian m. carlson [this message]
2021-10-23 15:40         ` Justus Ranvier
2021-10-23 20:49           ` Ævar Arnfjörð Bjarmason

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=YXP5rZT5IgFcMZs0@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=justus@opentransactions.org \
    --cc=mail@rkta.de \
    --cc=matheus.bernardino@usp.br \
    /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).