Skip to content

fix potential lock when sqlite #1647

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

Merged
merged 1 commit into from
May 5, 2017

Conversation

lunny
Copy link
Member

@lunny lunny commented Apr 30, 2017

related with #1434

@lunny lunny added the type/refactoring Existing code has been cleaned up. There should be no new functionality. label Apr 30, 2017
@lunny lunny added this to the 1.2.0 milestone Apr 30, 2017
@bkcsoft
Copy link
Member

bkcsoft commented May 3, 2017

LGTM

@tboerger tboerger added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label May 3, 2017
@lafriks
Copy link
Member

lafriks commented May 4, 2017

LGTM

@tboerger tboerger added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels May 4, 2017
@lunny lunny merged commit 0f3923c into go-gitea:master May 5, 2017
@lunny lunny deleted the lunny/fix_potential_lock_sqlite branch May 5, 2017 00:47
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/refactoring Existing code has been cleaned up. There should be no new functionality.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants