tests-clar/refs/branches/tracking.c


Log

Author Commit Date CI Message
Ben Straub 72629a10 2012-12-10T10:05:31 Clean up GCC build warnings
Vicent Martí e05ca13f 2012-12-05T11:47:19 Merge pull request #1115 from ben/struct-versions Version info for public structs
nulltoken 3da73c40 2012-11-29T21:33:31 Fix compilation warnings
Ben Straub f4fc9fdb 2012-11-29T12:26:40 Cleanup nitpicky things
nulltoken 37849a8e 2012-11-17T22:09:55 tracking: fix retrieval of the tracking ref of branch with empty merge and/or remote entry
nulltoken f1bd50d6 2012-11-17T22:07:30 tracking: remove code duplication in test
Sascha Cunz 9094d30b 2012-11-23T11:41:56 Reset all static variables to NULL in clar's __cleanup Without this change, any failed assertion in the second (or a later) test inside a test suite has a chance of double deleting memory, resulting in a heap corruption. See #1096 for details. This leaves alone the test cases where we "just" use cl_git_sandbox_init() and cl_git_sandbox_cleanup(). These methods already take good care to not double delete a repository. Fixes #1096
nulltoken e16fc07f 2012-09-13T22:22:40 refspec: No remote tracking ref from a fetchspec-less remote
nulltoken fb910281 2012-07-20T16:38:54 branch: introduce git_branch_tracking()