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

gc --auto: release pack files before auto packing #1769

Merged

Conversation

dscho
Copy link
Member

@dscho dscho commented Jul 27, 2018

Teach gc --auto to release pack files before auto packing the repository
to prevent failures when removing them.

Also teach the test 'fetching with auto-gc does not lock up' to complain
when it is no longer triggering an auto packing of the repository.

Fixes #500

Teach gc --auto to release pack files before auto packing the repository
to prevent failures when removing them.

Also teach the test 'fetching with auto-gc does not lock up' to complain
when it is no longer triggering an auto packing of the repository.

Fixes git-for-windows#500

Signed-off-by: Kim Gybels <kgybels@infogroep.be>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
@dscho
Copy link
Member Author

dscho commented Jul 27, 2018

/cc @kgybels (I would like to make you the reviewer once you accept, and then you should be able to merge this PR, maybe after the build finishes?).

@kgybels
Copy link

kgybels commented Jul 30, 2018

@dscho Why do we need to merge this to git-for-windows:master? What happens when the change gets to git:master?

@dscho
Copy link
Member Author

dscho commented Aug 1, 2018

Why do we need to merge this to git-for-windows:master?

The idea is to have it in Git for Windows early, in particular in a snapshot, so that the bug reporter can verify that the issue is fixed. You would not believe how many times we took fixes, and they were untested, and the new Git for Windows version came out, and the bug was not fixed. Of course, this also happened despite snapshots to test, and the bug reporters simply didn't. But I want us to at least offer this, as it is then not our fault that the fix was not correct.

What happens when the change gets to git:master?

The next merging rebase will drop it automatically, as it is already upstream.

@kgybels kgybels merged commit 9b68f5a into git-for-windows:master Aug 1, 2018
@gitster gitster deleted the kg/gc-auto-windows-workaround branch November 6, 2018 06:01
@gitster gitster restored the kg/gc-auto-windows-workaround branch November 6, 2018 06:25
@gitster gitster deleted the kg/gc-auto-windows-workaround branch August 16, 2019 20:19
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