mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Tessa L. H. Lovelace" <>
Subject: Using .gitignore symbolic links?
Date: Thu, 17 Jun 2021 19:34:40 -0700	[thread overview]
Message-ID: <> (raw)

The recent release candidate of Git (v2.32.0) hit my OS this week, and 
it included a line () on symbolic links for several specific files are 
now ignored.

Thank you for putting the changelogs in an accessible location, knowing 
that this was a known breaking change was useful in debugging why my 
workflows stopped working.

I have two concerns.

First, the error thrown is

 > "warning: unable to access '.gitignore': Too many levels of symbolic 

,,,which does not accurately represent what is happening.

I spent a bit of time convinced that I'd broken something with the 
symbolic links during setup, and an error such as "symbolic linking no 
longer allowed for 'filename'." would make more sense, given the change 
under discussion eliminates *any* use of symbolic links.

Secondly, and more personally important to me, a system administrator:
My repositories use symbolic links to allow a single .gitignore file to 
define my folder structure, allowing me to avoid hardcoding the 
repo-specific folder paths into my configs.

Is there a flag to disable this new behavior?

If not, this change means I need to update dozens of files, duplicates 
all, or completely rewrite my .gitignore files to have shyteloads of 
arbitrary file paths in them, which I'd rather not do.

Also, is there a justification for forcing this as the on-update 
default new behavior, when a user-querying behavior (such as with 'git 
pull' defaults as they've changed recently) exists?





Tessa L. H. Lovelace
office:		503.893.9709

             reply	other threads:[~2021-06-18  2:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  2:34 Tessa L. H. Lovelace [this message]
2021-06-18  6:44 ` Using .gitignore symbolic links? Robert Karszniewicz
2021-06-18 11:15 ` Ævar Arnfjörð Bjarmason
2021-06-18 12:55   ` Jeff King
2021-07-03 17:29   ` Tessa L.

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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

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).