user/sven/git.git/decorate.c, branch v2.6.1

hashmap: factor out getting a hash code from a SHA1

2014-07-07T20:56:24Z

Copying the first bytes of a SHA1 is duplicated in six places, however, the implications (the actual value would depend on the endianness of the platform) is documented only once. Add a properly documented API for this. Signed-off-by: Karsten Blees Signed-off-by: Junio C Hamano

decorate.c: compact table when growing

2013-05-16T18:51:08Z

When growing the table, take the opportunity to "compact" it by removing entries with NULL decoration. Users may have "removed" decorations by passing NULL to insert_decoration. An object's table entry can't actually be removed during normal operation, as it would break the linear hash collision search. But we can remove NULL decoration entries when rebuilding the table. Signed-off-by: Kevin Bracey Signed-off-by: Junio C Hamano

Unify signedness in hashing calls

2009-05-20T07:02:24Z

Our hash_obj and hashtable_index calls and functions were doing a lot of funny things with signedness. Unify all of it to 'unsigned int'. Signed-off-by: Dan McGee Signed-off-by: Junio C Hamano

Fix type-punning issues

2009-05-17T05:41:18Z

In these two places we are casting part of our unsigned char sha1 array into an unsigned int, which violates GCCs strict-aliasing rules (and probably other compilers). Signed-off-by: Dan McGee Signed-off-by: Junio C Hamano

decorate: allow const objects to be decorated

2008-08-20T20:30:49Z

We don't actually modify the struct object, so there is no reason not to accept const versions (and this allows other callsites, like the next patch, to use the decoration machinery). Signed-off-by: Jeff King Signed-off-by: Junio C Hamano

fast-export --export-marks: fix off by one error

2008-07-03T07:34:59Z

The export_marks() function iterated over a (potentially sparsely populated) hashtable, but it accessed it starting from offset 1 and one element beyond the end. Noticed by SungHyun Nam. Signed-off-by: Junio C Hamano

Fix a copy-n-paste bug in the object decorator code.

2007-04-21T02:16:12Z

Duh. When I did the object decorator thing, I made the "loop over the hash" function use the same logic for updating the hash, ie made them use if (++j >= size) j = 0; for both the hash update for both "insert" and "lookup" HOWEVER. For some inexplicable reason I had an extraneous j++; in the insert path (probably just from the fact that the old code there used j++; if (j >= size) j = 0; and when I made them use the same logic I just didn't remove the old extraneous line properly. This fixes it. Signed-off-by: Linus Torvalds Signed-off-by: Junio C Hamano

Add a generic "object decorator" interface, and make object refs use it

2007-04-16T23:51:09Z

This allows you to add an arbitrary "decoration" of your choice to any object. It's a space- and time-efficient way to add information to arbitrary objects, especially if most objects probably do not have the decoration. Signed-off-by: Linus Torvalds Signed-off-by: Junio C Hamano