[PATCH v1] git rev-list doesn't complain when repo is empty

From: Atousa Pahlevan Duprat Signed-off-by: Atousa Pahlevan Duprat --- builtin/rev-list.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/builtin/rev-list.c b/builtin/rev-list.c index d80d1ed..f71b87f 100644 --- a/builtin/rev-list.c

[PATCH v4 3/3] Move all the SHA1 implementations into one directory

From: Atousa Pahlevan Duprat The various SHA1 implementations were spread around in 3 directories. This makes it easier to understand what implementations are available at a glance. Signed-off-by: Atousa Pahlevan Duprat --- Makefile | 10

[PATCH v4 1/3] Provide another level of abstraction for the SHA1 utilities.

From: Atousa Pahlevan Duprat The git source uses git_SHA1_Update() and friends to call into the code that computes the hashes. This is can then be mapped directly to an implementation that computes the hash, such as platform_SHA1_Update(); or as we will do in a subsequent

[PATCH v4 2/3] Limit the size of the data block passed to SHA1_Update()

From: Atousa Pahlevan Duprat Use the previous commit's abstraction mechanism for SHA1 to support a chunked implementation of SHA1_Update() which limits the amount of data in the chunk passed to SHA1_Update(). This is enabled by using the SHA1_MAX_BLOCK_SIZE envvar to specify

[PATCH] Limit the size of the data block passed to SHA1_Update()

From: Atousa Pahlevan Duprat Some implementations of SHA_Updates have inherent limits on the max chunk size. SHA1_MAX_BLOCK_SIZE can be defined to set the max chunk size supported, if required. This is enabled for OSX CommonCrypto library and set to 1GiB. Signed-off-by:

[PATCH 1/2] Limit the size of the data block passed to SHA1_Update()

From: Atousa Pahlevan Duprat Some implementations of SHA_Updates have inherent limits on the max chunk size. SHA1_MAX_BLOCK_SIZE can be defined to set the max chunk size supported, if required. This is enabled for OSX CommonCrypto library and set to 1GiB. Signed-off-by:

[PATCH] Limit the size of the data block passed to SHA1_Update()

From: Atousa Pahlevan Duprat Some implementations of SHA_Updates have inherent limits on the max chunk size. SHA1_MAX_BLOCK_SIZE can be defined to set the max chunk size supported, if required. This is enabled for OSX CommonCrypto library and set to 1GiB. Signed-off-by: