Jeff King writes:
> I actually think all of that infrastructure could become part of
> Jonathan's consolidated lookup, too. We would just need:
>
> 1. A QUICK flag to avoid re-reading objects/pack when we don't find
> anything (which it looks like he already has).
>
> 2. A FRESHEN flag t
On Thu, Jun 15, 2017 at 10:50:46AM -0700, Junio C Hamano wrote:
> > if (!find_pack_entry(real, &e)) {
> > /* Most likely it's a loose object. */
> > - if (!sha1_loose_object_info(real, oi, flags)) {
> > + if (oi && !sha1_loose_object_info(real, oi, flags)) {
> >
On Thu, 15 Jun 2017 10:50:46 -0700
Junio C Hamano wrote:
> Jonathan Tan writes:
>
> > Looking at the 3 primary functions (sha1_object_info_extended,
> > read_object, has_sha1_file_with_flags), they independently implement
> > mechanisms such as object replacement, retrying the packed store afte
Jonathan Tan writes:
> Looking at the 3 primary functions (sha1_object_info_extended,
> read_object, has_sha1_file_with_flags), they independently implement
> mechanisms such as object replacement, retrying the packed store after
> failing to find the object in the packed store then the loose sto
In sha1_file.c, there are a few functions that provide information on an
object regardless of its storage (cached, loose, or packed). Looking
through all non-static functions in sha1_file.c that take in an unsigned
char * pointer, the relevant ones are:
- sha1_object_info_extended
- sha1_object_i
5 matches
Mail list logo
