delta/libgit2.git/tests/revwalk, branch ethomson/https_proxy github.com: libgit2/libgit2.git revwalk: fix memory leak in error handling 2019-05-10T10:27:47+00:00 Heiko Voigt hvoigt@hvoigt.net 2019-05-06T09:39:51+00:00 6990a4926161d668560968b8c75f9d7c3d180737 This is not implemented and should fail, but it should also not leak. To allow the memory debugger to find leaks and fix this one we test this. 
This is not implemented and should fail, but it should also not leak. To
allow the memory debugger to find leaks and fix this one we test this.
git_revwalk_push_range: do not crash if range is missing 2019-05-03T11:38:26+00:00 Heiko Voigt hvoigt@hvoigt.net 2019-04-26T13:59:49+00:00 d55bb479ddad2e8feaed7bf3e1773cf344db108c If someone passes just one ref (i.e. "master") and misses passing the range we should be nice and return an error code instead of crashing. 
If someone passes just one ref (i.e. "master") and misses passing the
range we should be nice and return an error code instead of crashing.
Fix a bunch of warnings 2019-01-06T06:26:18+00:00 lhchavez lhchavez@lhchavez.com 2019-01-06T06:12:48+00:00 7b453e7e39c6e27d63be0922a153e1cb47f33218 This change fixes a bunch of warnings that were discovered by compiling with `clang -target=i386-pc-linux-gnu`. It turned out that the intrinsics were not necessarily being used in all platforms! Especially in GCC, since it does not support __has_builtin. Some more warnings were gleaned from the Windows build, but I stopped when I saw that some third-party dependencies (e.g. zlib) have warnings of their own, so we might never be able to enable -Werror there. 
This change fixes a bunch of warnings that were discovered by compiling
with `clang -target=i386-pc-linux-gnu`. It turned out that the
intrinsics were not necessarily being used in all platforms! Especially
in GCC, since it does not support __has_builtin.

Some more warnings were gleaned from the Windows build, but I stopped
when I saw that some third-party dependencies (e.g. zlib) have warnings
of their own, so we might never be able to enable -Werror there.
object_type: use new enumeration names 2018-12-01T11:54:57+00:00 Edward Thomson ethomson@edwardthomson.com 2018-11-28T14:26:57+00:00 168fe39bea3368972a8b1a33d5908e73bc790c18 Use the new object_type enumeration names within the codebase. 
Use the new object_type enumeration names within the codebase.
revwalk: Allow changing hide_cb 2018-11-28T13:19:48+00:00 Eivind Fonn evfonn@gmail.com 2018-11-14T15:08:30+00:00 0836f0695ec1cb5ec45372bd3c7696bbd65cf8b7 Since git_revwalk objects are encouraged to be reused, a public interface for changing hide_cb is desirable. 
Since git_revwalk objects are encouraged to be reused, a public
interface for changing hide_cb is desirable.
Clear revwalk sorting when resetting 2018-06-22T16:25:14+00:00 Nika Layzell nika@thelayzells.com 2018-06-18T23:43:53+00:00 4fd81c537742ad3e805fc04a910e1a7c226cc904 Currently we fail to clear the sorting flag for revwalks when resetting. This caused a poor interaction with the limited flag during a recent patch. This patch clears the revwalk sorting flag and causes it to no longer persist over resets. 
Currently we fail to clear the sorting flag for revwalks when resetting.
This caused a poor interaction with the limited flag during a recent
patch. This patch clears the revwalk sorting flag and causes it to no
longer persist over resets.
revwalk: fix uninteresting revs sometimes not limiting graphwalk 2018-04-12T12:45:53+00:00 Patrick Steinhardt ps@pks.im 2018-04-12T12:32:27+00:00 54fd80e3f8d7850576c60fa8baf7269df3c9e6a3 When we want to limit our graphwalk, we use the heuristic of checking whether the newest limiting (uninteresting) revision is newer than the oldest interesting revision. We do so by inspecting whether the first item's commit time of the user-supplied list of revisions is newer than the last added interesting revision. This is wrong though, as the user supplied list is in no way guaranteed to be sorted by increasing commit dates. This could lead us to abort the revwalk early before applying all relevant limiting revisions, outputting revisions which should in fact have been hidden. Fix the heuristic by instead checking whether _any_ of the limiting commits was made earlier than the last interesting commit. Add a test. 
When we want to limit our graphwalk, we use the heuristic of checking
whether the newest limiting (uninteresting) revision is newer than the
oldest interesting revision. We do so by inspecting whether the first
item's commit time of the user-supplied list of revisions is newer than
the last added interesting revision. This is wrong though, as the user
supplied list is in no way guaranteed to be sorted by increasing commit
dates. This could lead us to abort the revwalk early before applying all
relevant limiting revisions, outputting revisions which should in fact
have been hidden.

Fix the heuristic by instead checking whether _any_ of the limiting
commits was made earlier than the last interesting commit. Add a test.
testrepo: add new branch 2018-02-24T00:54:39+00:00 Edward Thomson ethomson@edwardthomson.com 2018-02-20T00:32:38+00:00 18d9c8479f8534cc19765345560d2d39b8920a4d Add a new branch to the `testrepo` repository, where the `README` file has changed to executable. This branch enables typechange tests between the new `executable` branch and `master`. 
Add a new branch to the `testrepo` repository, where the `README` file
has changed to executable.  This branch enables typechange tests between
the new `executable` branch and `master`.
Skip uninteresting commits in revwalk timesort iterator 2017-03-09T13:01:10+00:00 Adam Niedzielski adamsunday@gmail.com 2017-03-09T13:01:10+00:00 c11c08a552cf4b21f1a1b95513788c8011b41c07 Fixes #4099 
Fixes #4099
tests: add merge-conflict branch for testrepo 2017-02-13T09:13:02+00:00 Patrick Steinhardt ps@pks.im 2015-11-10T14:53:09+00:00 8acc3b16efb3332596579b17b2046ecdeeac275a Add a new branch that causes a merge conflict to `testrepo` so that we are able to test merging in worktrees. 
Add a new branch that causes a merge conflict to `testrepo` so
that we are able to test merging in worktrees.