On Mar 20, 2015, at 15:02, Junio C Hamano wrote:
* bc/object-id (2015-03-13) 10 commits
- apply: convert threeway_stage to object_id
- patch-id: convert to use struct object_id
- commit: convert parts to struct object_id
- diff: convert struct combine_diff_path to object_id
- bulk-checkin.c: convert to use struct object_id
- zip: use GIT_SHA1_HEXSZ for trailers
- archive.c: convert to use struct object_id
- bisect.c: convert leaf functions to use struct object_id
- define utility functions for object IDs
- define a structure for object IDs
Identify parts of the code that knows that we use SHA-1 hash to
name our objects too much, and use (1) symbolic constants instead
of hardcoded 20 as byte count and/or (2) use struct object_id
instead of unsigned char [20] for object names.
Will cook in 'next'.
Has this been merged to 'next'? Even fetching github.com/gitster/
git.git I'm only seeing it in pu:
$ git rev-parse bc/object-id
d07d4ab401173a10173f2747cf5e0f074b6d2b39
$ git branch --contains d07d4ab401173a10173f2747cf5e0f074b6d2b39 --all
bc/object-id
jch
pu
remotes/github2/pu
remotes/gob-private/pu
remotes/gph/pu
remotes/ko/pu
remotes/repo/pu
-Kyle
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
