Re: Including object type and size in object id (Re: Git Merge contributor summit notes)

Jonathan Nieder writes: > This implies a limit on the object size (e.g. 5 bytes in your > example). What happens when someone wants to encode an object larger > than that limit? > > This also decreases the number of bits available for the hash, but > that shouldn't be a big

Re: Including object type and size in object id (Re: Git Merge contributor summit notes)

On 3/26/2018 5:00 PM, Jonathan Nieder wrote: Jeff Hostetler wrote: [long quote snipped] While we are converting to a new hash function, it would be nice if we could add a couple of fields to the end of the OID: the object type and the raw uncompressed object size. If would be nice if we

Including object type and size in object id (Re: Git Merge contributor summit notes)

(administrivia: please omit parts of the text you are replying to that are not relevant to the reply. This makes it easier to see what you're replying to, especially in mail readers that don't hide quoted text by the default) Hi Jeff, Jeff Hostetler wrote: [long quote snipped] > While we are