Revision 750bb32589ea157bfe522a66f814a0124c97c41b authored by Jeff King on 23 June 2020, 15:24:51 UTC, committed by Junio C Hamano on 24 June 2020, 02:56:26 UTC
When fast-export stores anonymized oids, it does so as binary strings. And while the anonymous mapping storage is binary-clean (at least as of the previous commit), this will become awkward when we start exposing more of it to the user. In particular, if we allow a method for retaining token "foo", then users may want to specify a hex oid as such a token. Let's just switch to storing the hex strings. The difference in memory usage is negligible (especially considering how infrequently we'd generally store an oid compared to, say, path components). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent b897bf5
| File | Mode | Size |
|---|---|---|
| files-backend.c | -rw-r--r-- | 86.1 KB |
| iterator.c | -rw-r--r-- | 10.5 KB |
| packed-backend.c | -rw-r--r-- | 44.4 KB |
| packed-backend.h | -rw-r--r-- | 1.2 KB |
| ref-cache.c | -rw-r--r-- | 14.0 KB |
| ref-cache.h | -rw-r--r-- | 8.9 KB |
| refs-internal.h | -rw-r--r-- | 24.3 KB |
Computing file changes ...
