- 05 Aug, 2014 1 commit
-
-
Jacques Germishuys committed
-
- 07 Jun, 2014 1 commit
-
-
Philip Kelley committed
-
- 08 May, 2014 1 commit
-
-
It seems that with the various recent changes to reference updating and reflog writing, that the thread safety of refdb updates has been reduced (either that or it was never thread safe and the window for error has increased). Either way, this test is now sometimes segfaulting which is no good, so let's disable the test for now. We don't really make any public promises about thread safety for this type of operation, so I think this is acceptable, at least in the short term.
Russell Belfer committed
-
- 17 Apr, 2014 1 commit
-
-
Russell Belfer committed
-
- 15 Jan, 2014 1 commit
-
-
Any well-behaved program should write a descriptive message to the reflog whenever it updates a reference. Let's make this more prominent by removing the version without the reflog parameters.
Carlos Martín Nieto committed
-
- 14 Nov, 2013 1 commit
-
-
Ben Straub committed
-
- 01 Nov, 2013 1 commit
-
-
Vicent Marti committed
-
- 29 Aug, 2013 1 commit
-
-
Carlos Martín Nieto committed
-
- 21 Aug, 2013 2 commits
-
-
Russell Belfer committed
-
This adds thread safety to the refdb_fs by using the new git_sortedcache object and also by relaxing the handling of some filesystem errors where the fs may be changed out from under us. This also adds some new threading tests that hammer on the refdb.
Russell Belfer committed
-