From: "James Bowes" <jbowes@dangerouslyinc.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org, "Shawn Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] rev-parse: Identify short sha1 sums correctly.
Date: Tue, 29 May 2007 21:09:50 -0400 [thread overview]
Message-ID: <3f80363f0705291809y23b1bf06j4076ecc09fe8c0d5@mail.gmail.com> (raw)
In-Reply-To: <7vtztv3zf1.fsf@assigned-by-dhcp.cox.net>
On 5/29/07, Junio C Hamano <junkio@cox.net> wrote:
> Thanks, James.
Glad to help when I can.
> This seems to fix the bug I mentioned about 'next' in the last
> "What's cooking" message. Also I have been seeing a segfault
> from rev-parse in t5500 (rev-parse --short hits the same issue,
> because the bug caused object name not to be abreviated) but
> that is also fixed with this patch.
>
> Will apply, instead of reverting the "lazy index loading".
>
>
>
-James
next prev parent reply other threads:[~2007-05-30 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 23:29 [PATCH] rev-parse: Identify short sha1 sums correctly James Bowes
2007-05-30 0:53 ` Junio C Hamano
2007-05-30 1:09 ` James Bowes [this message]
[not found] <1180478596243-git-send-email-jbowes@dangerouslyinc.com>
2007-05-29 23:40 ` Junio C Hamano
2007-05-30 1:58 ` Shawn O. Pearce
2007-05-30 2:02 ` Shawn O. Pearce
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=3f80363f0705291809y23b1bf06j4076ecc09fe8c0d5@mail.gmail.com \
--to=jbowes@dangerouslyinc.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.org \
/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;
as well as URLs for NNTP newsgroup(s).