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

Rename EVERYTHING #22

Closed
derrickstolee opened this issue Aug 8, 2019 · 0 comments · Fixed by #38
Closed

Rename EVERYTHING #22

derrickstolee opened this issue Aug 8, 2019 · 0 comments · Fixed by #38
Assignees

Comments

@derrickstolee
Copy link
Contributor

New name TBD.

  • Replace all instances of "GVFS" and "VFSForGit" (and variants) in the filenames using an exact-rename commit.
  • Drop the base "GVFS" folder in the same commit.
  • Perform text-based replacement of "GVFS", "VFSForGit", and variants in most places (some things need to stay, such as the Git package name).
@derrickstolee derrickstolee self-assigned this Aug 8, 2019
derrickstolee added a commit that referenced this issue Aug 11, 2019
Resolves #22.

Our new name is "Scalar". This replaces as many instances of the old GVFS, gvfs, VFS for Git, VFSFORGIT, vfsforgit, etc. with "Scalar", "scalar", or "SCALAR" as appropriate.

The commits are organized as follows:

1. `[RENAME] Rename all files`. This is a mechanical `find` and `mv` operation, done by a script. No blobs are changed, so `--follow-renames` should get exact values here, unless there are _exact_ duplicate files in the repo. This also flattens the repo, so the old "GVFS/GVFS.*" pattern is now just "Scalar.*".

2. `[REPLACE] Replace old name in all files`. This is an attempt to automatically replace all the name strings in the contents of the files. Skips some binary file types.

The remaining commits attempt to group the reaction work required to respond to those changes.
derrickstolee added a commit that referenced this issue Aug 29, 2019
More fallout from #22. The script to replace GVFS with Scalar didn't catch the `.rc` file, so it had trouble on these version strings. I found this is affecting how the read object hook appears in Task Manager.
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 a pull request may close this issue.

1 participant