- 09 Mar, 2017 1 commit
-
-
Fixes #4099
Adam Niedzielski committed
-
- 13 Feb, 2017 1 commit
-
-
Add a new branch that causes a merge conflict to `testrepo` so that we are able to test merging in worktrees.
Patrick Steinhardt committed
-
- 02 Feb, 2017 1 commit
-
-
Adam Niedzielski committed
-
- 06 Oct, 2016 2 commits
-
-
We had some home-grown logic to figure out which objects to show during the revision walk, but it was rather inefficient, looking over the same list multiple times to figure out when we had run out of interesting commits. We now use the lists in a smarter way. We also introduce the slop mechanism to determine when to stpo looking. When we run out of interesting objects, we continue preparing the walk for another 5 rounds in order to make it less likely that we miss objects in situations with complex graphs.
Carlos Martín Nieto committed -
Introduce some tests that show some commits, while hiding some commits that have a timestamp older than the common ancestors of these two commits.
Edward Thomson committed
-
- 21 Oct, 2015 1 commit
-
-
Vicent Marti committed
-
- 14 Oct, 2015 1 commit
-
-
We moved the "main" parsing to use 64 bits for the timestamp, but the quick parsing for the revwalk did not. This means that for large timestamps we fail to parse the time and thus the walk. Move this parser to use 64 bits as well.
Carlos Martín Nieto committed
-
- 08 Apr, 2015 1 commit
-
-
When we hide a commit which we later push into the revwalk, we do not handle this well and return commits which we should not.
Carlos Martín Nieto committed
-
- 03 Feb, 2015 1 commit
-
-
Edward Thomson committed
-
- 16 Sep, 2014 1 commit
-
-
Ciro Santilli committed
-
- 31 Mar, 2014 1 commit
-
-
Anurag Gupta committed
-
- 12 Mar, 2014 1 commit
-
-
If the pqueue comparison fn returned just 0 or 1 (think "a<b") then the sort order of returned items could be wrong because there was a "< 0" that really needed to be "<= 0". Yikes!!!
Russell Belfer committed
-
- 05 Feb, 2014 3 commits
-
-
This used to be broken, let's make sure we don't break this use-case.
Carlos Martín Nieto committed -
Pushing a whole namespace can cause us to attempt to push non-committish objects. Catch this situation and special-case it for ignoring this.
Carlos Martín Nieto committed -
This shows that pusing a whole namespace can be problematic.
Carlos Martín Nieto committed
-
- 14 Nov, 2013 1 commit
-
-
Ben Straub committed
-
- 07 Aug, 2013 1 commit
-
-
Ben Straub committed
-
- 22 Jul, 2013 2 commits
-
-
The new tests don't always want to use the same fixture data as the old ones so this makes it configurable on a per-test basis.
Russell Belfer committed -
The git_reference_next API silently skips invalid references when scanning the loose refs. The git_reference_next_name API should skip the same ones even though it isn't creating the reference object. This adds a test with a an invalid loose reference and makes sure that both APIs skip the same entries and generate the same results.
Russell Belfer committed
-
- 07 Apr, 2013 1 commit
-
-
All the hard work is already in revparse. Signed-off-by: Greg Price <price@mit.edu>
Greg Price committed
-
- 31 Mar, 2013 2 commits
-
-
Signed-off-by: Greg Price <price@mit.edu>
Greg Price committed -
The purported command output was already inaccurate, as the refs aren't where it shows. In any event, the labels a reader of this file really needs are the indices used in commit_sorting_*, to make it possible to understand them by referring directly from those arrays to the diagram rather than from the index arrays, to commit_ids, to the diagram. Add those. Signed-off-by: Greg Price <price@mit.edu>
Greg Price committed
-
- 23 Nov, 2012 1 commit
-
-
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
Sascha Cunz committed
-
- 27 Aug, 2012 1 commit
-
-
Check the type of the pushed object immediately instead of starting the walk and failing in between.
Michael Schubert committed
-
- 11 Jul, 2012 1 commit
-
-
nulltoken committed
-
- 17 May, 2012 1 commit
-
-
Vicent Martí committed
-
- 12 Apr, 2012 2 commits
-
-
Nothing should be hidden and this shouldn't bother the merge base calculation.
Carlos Martín Nieto committed -
The code was already there, so factor it out and let users push an OID by giving it a reference name. Only refs to commits are supported. Annotated tags will throw an error.
Carlos Martín Nieto committed
-
- 27 Feb, 2012 4 commits
-
-
Carlos Martín Nieto committed
-
It's not unusual to want the walker to act on HEAD, so add a convencience function for the case that the user doesn't already have a resolved HEAD reference.
Carlos Martín Nieto committed -
Carlos Martín Nieto committed
-
Carlos Martín Nieto committed
-
- 01 Jul, 2011 1 commit
-
-
Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
Kirill A. Shutemov committed
-
- 16 Jun, 2011 1 commit
-
-
Yeah. Finally. Fuck the old names, this ain't POSIX and they don't make any sense at all.
Vicent Marti committed
-
- 16 Mar, 2011 1 commit
-
-
The "oid.h" header is now included instead of "object.h". The old "revwalk.h" header has been removed; it was empty.
Vicent Marti committed
-
- 15 Mar, 2011 1 commit
-
-
The `reset` call now removes the pushed commits so we can reuse the revwalker. The API documentation has been updated with the details.
Vicent Marti committed
-
- 14 Mar, 2011 1 commit
-
-
The new revision walker uses an internal Commit object storage system, custom memory allocator and much improved topological and time sorting algorithms. It's about 20x times faster than the previous implementation when browsing big repositories. The following external API calls have changed: `git_revwalk_next` returns an OID instead of a full commit object. The initial call to `git_revwalk_next` is no longer blocking when iterating through a repo with a time-sorting mode. Iterating with Topological or inverted modes still makes the initial call blocking to preprocess the commit list, but this block should be mostly unnoticeable on most repositories (topological preprocessing times at 0.3s on the git.git repo). `git_revwalk_push` and `git_revwalk_hide` now take an OID instead of a full commit object.
Vicent Marti committed
-
- 03 Mar, 2011 1 commit
-
-
Tests are now declared with detailed descriptions and a short test name: BEGIN_TEST(the_test0, "this is an example test that does something") ... END_TEST Modules are declared through a simple macro interface: BEGIN_MODULE(mod_name) ADD_TEST(the_test0); ... END_MODULE Error messages when tests fail have been greatly improved. Signed-off-by: Vicent Marti <tanoku@gmail.com>
Vicent Marti committed
-
- 05 Feb, 2011 1 commit
-
-
git_revwalk_next now returns an error code when the iteration is over. git_repository_index now returns an error code when the index file could not be opened. Signed-off-by: Vicent Marti <tanoku@gmail.com>
Vicent Marti committed
-
- 02 Feb, 2011 1 commit
-
-
NIH Enterprises presents: a new testing system based on CuTesT, which is faster than our previous one and fortunately uses no preprocessing on the source files, which means we can run that from CMake. The test suites have been gathered together into bigger files (one file per suite, testing each of the different submodules of the library). Signed-off-by: Vicent Marti <tanoku@gmail.com>
Vicent Marti committed
-