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

fixup! pager: fix order of atexit() calls #119

Merged
merged 1 commit into from
Feb 14, 2019
Merged

fixup! pager: fix order of atexit() calls #119

merged 1 commit into from
Feb 14, 2019

Conversation

benpeart
Copy link

A bit of housekeeping to reduce the number of patches in our fork. This reverts commit 3f58806 as it no longer fixes the underlying issue so there is no reason to keep hauling it along with every release.

Signed-off-by: Ben Peart benpeart@microsoft.com

This reverts commit 3f58806 as it no longer fixes the underlying issue.

Signed-off-by: Ben Peart <benpeart@microsoft.com>
Copy link
Member

@kewillford kewillford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was there any other issues that we were fixing with this besides the GIT_TRACE_PERFORMANCE? Like that had to do with the post command?

@benpeart
Copy link
Author

Was there any other issues that we were fixing with this besides the GIT_TRACE_PERFORMANCE? Like that had to do with the post command?

IIRC was just to enable getting the trace output. It doesn't have any impact on the post-command hook. I've verified it still passes the pre and post-command hook tests just to be sure.

@benpeart benpeart merged commit 8af1f39 into microsoft:vfs-2.20.1 Feb 14, 2019
@benpeart benpeart deleted the revert-pager-atexit branch February 14, 2019 14:27
@dscho
Copy link
Member

dscho commented Feb 18, 2019

Did it not also have something to do with tracing in the post-command hook?

@benpeart
Copy link
Author

I discovered (and fixed) the problem debugging the post-command hook but the post-command hook itself doesn't need/require it. The "fix" got broken at some point since then and doesn't work anymore anyway. :(

@dscho
Copy link
Member

dscho commented Feb 20, 2019

the post-command hook itself doesn't need/require it.

Okay, then. Thanks for the clarification!

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.

3 participants