Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ignore *.uuid files #371

Merged
merged 1 commit into from
Sep 18, 2019
Merged

ignore *.uuid files #371

merged 1 commit into from
Sep 18, 2019

Conversation

lebel
Copy link
Contributor

@lebel lebel commented Sep 6, 2019

Description

When using the patched-fonts directory directly with let say Gnome, a bunch of *.uuid files are created and polluting the git environment with new files. This make sure those are ignored.

Requirements / Checklist

  • [ * ] Read the Contributing Guidelines
  • [ * ] Read or at least glanced at the FAQ
  • [ * ] Read or at least glanced at the Wiki
  • [ N/A ] Scripts execute without error (if necessary):
    • If any of the scripts were modified they have been tested and execute without error, e.g.:
      • ./font-patcher Inconsolata.otf --fontawesome --octicons --pomicons
      • ./gotta-patch-em-all-font-patcher\!.sh Hermit
  • [ N/A ] Extended the README and documentation if necessary, e.g. You added a new font please update the table

What does this Pull Request (PR) do?

add *.uuid into the .gitignore file.

How should this be manually tested?

Any background context you can provide?

What are the relevant tickets (if any)?

Screenshots (if appropriate or helpful)

@ryanoasis
Copy link
Owner

I don't fully understand but this won't hurt anything to add it.

A bit of Googling did lead to some info after a few tries. Mostly what I was able to find was something related to fontconfig generating these files

@ryanoasis ryanoasis added this to the v2.1.0 milestone Sep 18, 2019
@ryanoasis ryanoasis merged commit 243278b into ryanoasis:master Sep 18, 2019
LNKLEO pushed a commit to LNKLEO/Nerd that referenced this pull request Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants