delta/libgit2.git/tests/threads/refdb.c, branch cmn/submodule-refactor github.com: libgit2/libgit2.git Remove the signature from ref-modifying functions 2015-03-03T13:40:50+00:00 Carlos Martín Nieto cmn@dwim.me 2015-01-07T12:23:05+00:00 659cf2029f322ea876d663d85783b48945227e8f The signature for the reflog is not something which changes dynamically. Almost all uses will be NULL, since we want for the repository's default identity to be used, making it noise. In order to allow for changing the identity, we instead provide git_repository_set_ident() and git_repository_ident() which allow a user to override the choice of signature. 
The signature for the reflog is not something which changes
dynamically. Almost all uses will be NULL, since we want for the
repository's default identity to be used, making it noise.

In order to allow for changing the identity, we instead provide
git_repository_set_ident() and git_repository_ident() which allow a user
to override the choice of signature.
Use p_snprintf also in tests 2014-08-05T18:51:59+00:00 Jacques Germishuys jacquesg@striata.com 2014-07-12T12:44:58+00:00 c7dd0a56bf81fa93327a1ec3c949a7d59a53f40d 






Win32: Fix object::cache::threadmania test on x64
2014-06-07T16:51:48+00:00

Philip Kelley
phkelley@microsoft.com

2014-06-07T16:51:48+00:00

fb5917679dd1cc0ee50d1d88893c07cbcd82471f












Disable threads::refdb::edit_while_iterate test
2014-05-08T22:01:07+00:00

Russell Belfer
rb@github.com

2014-05-08T22:01:07+00:00

bb45e39063669514b84ac5b47c3520cfe99396c3

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.





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.







Some memory leak fixes
2014-04-17T22:04:42+00:00

Russell Belfer
rb@github.com

2014-04-17T21:35:29+00:00

8303827226db114a1157e6173e731f316c217851












refs: remove the _with_log differentiation
2014-01-15T12:32:43+00:00

Carlos Martín Nieto
cmn@dwim.me

2014-01-15T11:51:31+00:00

0b28217bdae4fd64f5b6b8f4cb8a6139518d037e

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.





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.







Rename tests-clar to tests
2013-11-14T22:05:52+00:00

Ben Straub
bs@github.com

2013-11-14T22:05:52+00:00

1782038144ef3413831801bb9c2f3038a84ac6f4