delta/libgit2.git/src/pqueue.c, branch fileops github.com: libgit2/libgit2.git cleanup: remove trailing spaces 2011-07-01T16:02:56+00:00 Kirill A. Shutemov kirill@shutemov.name 2011-06-30T16:52:34+00:00 932d1baf294aaacfd5a99e7758a3c08d8ffc22ab Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name> 
Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
Change the Revwalk reset behavior to the old version 2011-03-15T23:53:25+00:00 Vicent Marti tanoku@gmail.com 2011-03-15T23:53:25+00:00 36aaf1ff1a8540c364050f62f19f3021b6e121eb The `reset` call now removes the pushed commits so we can reuse the revwalker. The API documentation has been updated with the details. 
The `reset` call now removes the pushed commits so we can reuse
the revwalker. The API documentation has been updated with the details.
Rewrite the Revision Walker 2011-03-14T21:52:15+00:00 Vicent Marti tanoku@gmail.com 2011-03-08T12:57:03+00:00 71db842fac3ba8582255bc5b61361ddef08ef105 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. 
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.