From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, James Bowes <jbowes@dangerouslyinc.com>
Subject: Re: [PATCH] rev-parse: Identify short sha1 sums correctly.
Date: Tue, 29 May 2007 22:02:36 -0400 [thread overview]
Message-ID: <20070530020236.GI7044@spearce.org> (raw)
In-Reply-To: <7vabvn5hca.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> James Bowes <jbowes@dangerouslyinc.com> writes:
>
> > find_short_packed_object was not loading the pack index files.
> > Teach it to do so.
> >
> > Signed-off-by: James Bowes <jbowes@dangerouslyinc.com>
>
> I think this is the proper fix of the problem I was unhappy
> about with 'next'
Actually this bug is exactly the reason why I *always* run 'next'
in production use on all of my systems, and why I also get a number
of coworkers to run it. Many people beating on the same code in
weird ways notice things.
Today I found this because I have a shell script that tried to
do something of the form "git checkout v1.8.0-18-g18as1f' and Git
couldn't believe that was a revision... It held up day-job work
for an hour while I tracked it down, but I did catch it. ;-)
--
Shawn.
next prev parent reply other threads:[~2007-05-30 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1180478596243-git-send-email-jbowes@dangerouslyinc.com>
2007-05-29 23:40 ` [PATCH] rev-parse: Identify short sha1 sums correctly Junio C Hamano
2007-05-30 1:58 ` Shawn O. Pearce
2007-05-30 2:02 ` Shawn O. Pearce [this message]
2007-05-29 23:29 James Bowes
2007-05-30 0:53 ` Junio C Hamano
2007-05-30 1:09 ` James Bowes
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=20070530020236.GI7044@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jbowes@dangerouslyinc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.