https://github.com/git/git
Revision 9da87231905913e9e33b30bbe92b54037a6b30ca authored by David Glasser on 16 October 2017, 23:09:59 UTC, committed by David Glasser on 17 October 2017, 09:43:55 UTC
The docs claim that filters are applied in the listed order, so
subdirectory-filter should come first.

For consistency, apply the same order to the SYNOPSIS and the script's usage, as
well as the switch while parsing arguments.

Add missing --prune-empty to the script's usage.

Signed-off-by: David Glasser <glasser@davidglasser.net>
1 parent 4010f1d
Raw File
Tip revision: 9da87231905913e9e33b30bbe92b54037a6b30ca authored by David Glasser on 16 October 2017, 23:09:59 UTC
doc: list filter-branch subdirectory-filter first
Tip revision: 9da8723
sha1dc_git.c
/*
 * This code is included at the end of sha1dc/sha1.c with the
 * SHA1DC_CUSTOM_TRAILING_INCLUDE_SHA1_C macro.
 */

void git_SHA1DCFinal(unsigned char hash[20], SHA1_CTX *ctx)
{
	if (!SHA1DCFinal(hash, ctx))
		return;
	die("SHA-1 appears to be part of a collision attack: %s",
	    sha1_to_hex(hash));
}

void git_SHA1DCUpdate(SHA1_CTX *ctx, const void *vdata, unsigned long len)
{
	const char *data = vdata;
	/* We expect an unsigned long, but sha1dc only takes an int */
	while (len > INT_MAX) {
		SHA1DCUpdate(ctx, data, INT_MAX);
		data += INT_MAX;
		len -= INT_MAX;
	}
	SHA1DCUpdate(ctx, data, len);
}
back to top