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

A new release? #38

Closed
Felixoid opened this issue Dec 7, 2023 · 5 comments
Closed

A new release? #38

Felixoid opened this issue Dec 7, 2023 · 5 comments

Comments

@Felixoid
Copy link

Felixoid commented Dec 7, 2023

Hello. It looks like it is worth spinning a new release, there's been some useful changes since 2.3.0

@woefe
Copy link
Owner

woefe commented Dec 22, 2023

👍

after #41 is merged

@telemachus
Copy link
Contributor

telemachus commented Dec 23, 2023

One other random thought: git status can take a --no-optional-locks flag, and I wonder if that's better, worse, any different than prepending the command with GIT_OPTIONAL_LOCKS=0. (The --no-optional-locks seems to have been available since 2017 so it shouldn't be a problem in terms of different versions of git.)

Sorry if this isn't the best place to put this note, but I figure it may make sense to consider before a new release.

@woefe
Copy link
Owner

woefe commented Dec 23, 2023

Setting the env var is backwards compatible, hence I won't change it for the next release. I've added a TODO item for #42 to replace it with the command option once we require a newer Git version anyways.

@telemachus
Copy link
Contributor

👍

after #41 is merged

Just to make everything up to date, this should now track #43.

@woefe
Copy link
Owner

woefe commented Feb 24, 2024

@woefe woefe closed this as completed Feb 24, 2024
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

3 participants