git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Robert Karszniewicz <avoidr@posteo.de>
To: "Tessa L. H. Lovelace" <tessa@assorted.tech>
Cc: git@vger.kernel.org
Subject: Re: Using .gitignore symbolic links?
Date: Fri, 18 Jun 2021 06:44:05 +0000	[thread overview]
Message-ID: <YMxAteKYn0qf/YNj@BDZ> (raw)
In-Reply-To: <1623983680.3494.0@smtp.dreamhost.com>

On Thu, Jun 17, 2021 at 07:34:40PM -0700, Tessa L. H. Lovelace wrote:
> 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.

Hmm, it sounds like `core.excludesFile` described in git-config(1) could
do what you need:

  core.excludesFile
      Specifies the pathname to the file that contains patterns to
      describe paths that are not meant to be tracked, in addition to
      .gitignore (per-directory) and .git/info/exclude. Defaults to
      $XDG_CONFIG_HOME/git/ignore. If $XDG_CONFIG_HOME is either not set
      or empty, $HOME/.config/git/ignore is used instead. See
      gitignore(5).

Regards,
Robert Karszniewicz

  reply	other threads:[~2021-06-18  6:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  2:34 Using .gitignore symbolic links? Tessa L. H. Lovelace
2021-06-18  6:44 ` Robert Karszniewicz [this message]
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:
  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=YMxAteKYn0qf/YNj@BDZ \
    --to=avoidr@posteo.de \
    --cc=git@vger.kernel.org \
    --cc=tessa@assorted.tech \
    /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).