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

Add support for git 2.38+ automation for performance optimization (scalar) #371

Open
gdubicki opened this issue Oct 18, 2022 · 4 comments
Open

Comments

@gdubicki
Copy link
Member

Is your feature request related to a problem? Please describe.

In git 2.38 a new tool has been bundled, scalar, that allows automating enabling the performance optimization features for existing git repos.

It would be nice for tsrc to support this tool to automatically:

  • start managing repos with scalar (scalar register),
  • update the config of all scalar-manager repositories after git update (scalar reconfigure -a).

Perhaps tsrc could also start using scalar clone instead of git clone which would do a sparse checkout and start to manage the repo with scalar.

Describe the solution you'd like

tsrc could automatically run the above commands if it detects git v. 2.38+. It could detect git version update by storing it in a dot file and then run the config update.

@gdubicki
Copy link
Member Author

@gdubicki
Copy link
Member Author

gdubicki commented Oct 19, 2022

We can already use tsrc foreach to make use of scalar easier:

# -j1 because it writes to a git config file, so it's not a good idea to parallelise
tsrc foreach -j1 scalar register
scalar  reconfigure -a

@dmerejkowsky
Copy link
Collaborator

tsrc could automatically run the above commands if it detects git v. 2.38+. It could detect git version update by storing it in a dot file and then run the config update.

Not sure this is a right idea. I think scalar exists as a standalone tool for a good reason.

@dmerejkowsky
Copy link
Collaborator

dmerejkowsky commented Oct 20, 2022

Feel free to add something in the documentation so that users of tsrc learn about this possibility, though :)

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

No branches or pull requests

2 participants