git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Justus Ranvier <justus@opentransactions.org>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
	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 22:49:05 +0200	[thread overview]
Message-ID: <211023.86k0i3ihwz.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <e5a6dfa5-617f-5b5b-6803-45d36b3de53e@opentransactions.org>


On Sat, Oct 23 2021, Justus Ranvier wrote:

> On 10/23/21 04:01, brian m. carlson wrote:
>> For example, I
>
> I'm glad that works for you and whatever organizations you happen to
> be involved in. I'm sure you're happy that git taking away this
> capability did not impact your workflow.
>
> Other people have different use cases and operate under different sets
> of constraints and are considerably inconvenienced when functionality 
> that has worked for many years is suddenly removed from a core piece
> of software like git.

I've workd on repos that had the union of every editor tempfile under
the sun in the .gitignore, it didn't really cause any practical
problems, they tend not to conflict with "real" filenames.

As for the .gitignore problem I think it's very much in the state of
"patches welcome", see a previous summary of mine at :
https://lore.kernel.org/git/87o8c34dq6.fsf@evledraar.gmail.com/

I.e. I don't think anyone should consider the current behavior to be set
in stone, and certainly not when it comes to potential opt-in
configuration.

      reply	other threads:[~2021-10-23 20:52 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
2021-10-23 15:40         ` Justus Ranvier
2021-10-23 20:49           ` Ævar Arnfjörð Bjarmason [this message]

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=211023.86k0i3ihwz.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=justus@opentransactions.org \
    --cc=mail@rkta.de \
    --cc=matheus.bernardino@usp.br \
    --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.
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).