delta/libgit2.git/src/pack.c, branch peff/binary-search-do-while github.com: libgit2/libgit2.git buffer: use `git_buf_init` with length 2017-06-08T09:58:23+00:00 Patrick Steinhardt ps@pks.im 2017-06-07T08:20:44+00:00 a693b8734941889bc9a4c31752d317658162246a The `git_buf_init` function has an optional length parameter, which will cause the buffer to be initialized and allocated in one step. This can be used instead of static initialization with `GIT_BUF_INIT` followed by a `git_buf_grow`. This patch does so for two functions where it is applicable. 
The `git_buf_init` function has an optional length parameter, which will
cause the buffer to be initialized and allocated in one step. This can
be used instead of static initialization with `GIT_BUF_INIT` followed by
a `git_buf_grow`. This patch does so for two functions where it is
applicable.
buffer: rely on `GITERR_OOM` set by `git_buf_try_grow` 2017-06-08T09:58:22+00:00 Patrick Steinhardt ps@pks.im 2017-06-07T08:05:54+00:00 97eb5ef0262bc0acf2ce66481105960b79e10ed7 The function `git_buf_try_grow` consistently calls `giterr_set_oom` whenever growing the buffer fails due to insufficient memory being available. So in fact, we do not have to do this ourselves when a call to any buffer-growing function has failed due to an OOM situation. But we still do so in two functions, which this patch cleans up. 
The function `git_buf_try_grow` consistently calls `giterr_set_oom`
whenever growing the buffer fails due to insufficient memory being
available. So in fact, we do not have to do this ourselves when a call
to any buffer-growing function has failed due to an OOM situation. But
we still do so in two functions, which this patch cleans up.
pack: fix looping over cache entries 2017-02-22T16:29:00+00:00 Jason Haslam jason@scitools.com 2017-02-22T16:29:00+00:00 685f22519c617e087a74b0754a10ceebc1ec9d77 Fixes a regression from #4092. This is a crash on 32-bit and I assume that it doesn't do the right thing on 64-bit either. MSVC emits a warning for this, but of course, it's easy to get lost among all of the similar 'possible loss of data' warnings. 
Fixes a regression from #4092. This is a crash on 32-bit and I assume that
it doesn't do the right thing on 64-bit either. MSVC emits a warning for this,
but of course, it's easy to get lost among all of the similar 'possible loss
of data' warnings.
 offmap: remove GIT__USE_OFFMAP macro 2017-02-17T10:41:06+00:00 Patrick Steinhardt ps@pks.im 2017-02-02T10:58:48+00:00 8f5fe903d629309cf711bf3c7a0c8e9b6826b0a0 






oidmap: remove GIT__USE_OIDMAP macro
2017-02-17T10:41:06+00:00

Patrick Steinhardt
ps@pks.im

2017-01-27T14:23:15+00:00

0d71690549b918d0aafc5873229661a43eee9eed












khash: avoid using `kh_key`/`kh_val` as lvalue
2017-02-17T10:41:06+00:00

Patrick Steinhardt
ps@pks.im

2017-01-27T13:05:10+00:00

85d2748c6f75bd810c7376647c8ae32984b5e3bb












khash: avoid using `kh_put` directly
2017-02-17T10:41:06+00:00

Patrick Steinhardt
ps@pks.im

2017-01-25T14:31:12+00:00

f31cb45ad2ca46cc743dfadf5ac8b916cbe4ea9c












khash: avoid using `kh_del` directly
2017-02-17T10:41:06+00:00

Patrick Steinhardt
ps@pks.im

2017-01-25T13:41:17+00:00

a8cd560b10149208aabcfe515b2e1b6c5be6388f












khash: avoid using `kh_val`/`kh_value` directly
2017-02-17T10:41:06+00:00

Patrick Steinhardt
ps@pks.im

2017-01-25T13:26:58+00:00

cb18386f72f07fc7316a0be892b98185d4aef7ce












khash: avoid using `kh_get` directly
2017-02-17T10:41:06+00:00

Patrick Steinhardt
ps@pks.im

2017-01-25T13:14:32+00:00

a853c5272359f7b5b1f0648cf16cefe7434840b2