From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Test for recent rev-parse $abbrev_sha1 regression
Date: Wed, 30 May 2007 01:58:06 -0400 [thread overview]
Message-ID: <20070530055806.GQ7044@spearce.org> (raw)
In-Reply-To: <7vlkf6508y.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
>
> > My recent patch "Lazily open pack index files on demand" caused a
> > regression in the case of parsing abbreviated SHA-1 object names.
> > Git was unable to translate the abbreviated name into the full name
> > if the object was packed, as the pack .idx files were not opened
> > before being accessed.
>
> Thanks. As long as we catch it before it goes to 'master', it
> is not a regression ;-)
Good point. Next time I won't call it a regression.
But to me, anything that hits 'next' that breaks Git this badly is
a regression. Why? Because I run my production repositories off
next, that's why. Of course I do this to exercise next more fully...
to prevent this sort of stuff from getting to master. ;-)
For what its worth, I'm going through the code again and auditing
our use of the index related variables in packed_git that are now
lazily loaded. I'm not seeing anything that is critical. I do
have two minor patches queued up, but they are just to make things
look prettier. Will send soon.
--
Shawn.
next prev parent reply other threads:[~2007-05-30 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 4:50 [PATCH] Test for recent rev-parse $abbrev_sha1 regression Shawn O. Pearce
2007-05-30 5:49 ` Junio C Hamano
2007-05-30 5:58 ` Shawn O. Pearce [this message]
2007-05-30 6:28 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070530055806.GQ7044@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox