1. 02 Feb, 2018 1 commit
  2. 20 Dec, 2017 2 commits
  3. 03 Jul, 2017 1 commit
    • Make sure to always include "common.h" first · 0c7f49dd
      Next to including several files, our "common.h" header also declares
      various macros which are then used throughout the project. As such, we
      have to make sure to always include this file first in all
      implementation files. Otherwise, we might encounter problems or even
      silent behavioural differences due to macros or defines not being
      defined as they should be. So in fact, our header and implementation
      files should make sure to always include "common.h" first.
      
      This commit does so by establishing a common include pattern. Header
      files inside of "src" will now always include "common.h" as its first
      other file, separated by a newline from all the other includes to make
      it stand out as special. There are two cases for the implementation
      files. If they do have a matching header file, they will always include
      this one first, leading to "common.h" being transitively included as
      first file. If they do not have a matching header file, they instead
      include "common.h" as first file themselves.
      
      This fixes the outlined problems and will become our standard practice
      for header and source files inside of the "src/" from now on.
      Patrick Steinhardt committed
  4. 29 Dec, 2016 1 commit
  5. 16 Nov, 2016 1 commit
    • use `giterr_set_str()` wherever possible · 65b78ea3
      `giterr_set()` is used when it is required to format a string, and since
      we don't really require it for this case, it is better to stick to
      `giterr_set_str()`.
      
      This also suppresses a warning(-Wformat-security) raised by the compiler.
      
      Signed-off-by: Pranit Bauva <pranit.bauva@gmail.com>
      Pranit Bauva committed
  6. 26 May, 2016 2 commits
  7. 13 Feb, 2015 2 commits
  8. 26 Apr, 2014 1 commit
    • zstream: grow based on used memory rather than allocated · c7f86efb
      When deflating data, we might need to grow the buffer. Currently we
      add a guess on top of the currently-allocated buffer size.
      
      When we re-use the buffer, it already has some memory allocated; adding
      to that means that we always grow the buffer regardless of how much we
      need to use.
      
      Instead, increase on top of the currently-used size. This still leaves
      us with the allocated size of the largest object we compress, but it's a
      minor pain compared to unbounded growth.
      
      This fixes #2285.
      Carlos Martín Nieto committed
  9. 30 Jan, 2014 3 commits
  10. 26 Jan, 2014 1 commit
  11. 14 Jan, 2014 2 commits