From: Jonathan del Strother <maillist@steelskies.com>
To: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Jens.Lehmann@web.de
Subject: Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash
Date: Sat, 30 Jan 2010 00:46:17 +0000 [thread overview]
Message-ID: <57518fd11001291646l5b0b581dm553689232b0910e8@mail.gmail.com> (raw)
In-Reply-To: <7vzl3wiz59.fsf@alter.siamese.dyndns.org>
On 29 January 2010 17:44, Junio C Hamano <gitster@pobox.com> wrote:
> Jonathan del Strother <maillist@steelskies.com> writes:
>
>> Heya,
>>
>> git-stash in v1.7.0-rc0 gives me several hundred lines of :
>> The previous build I was using -
>> 5b15950ac414a8a2d4f5eb480712abcc9fe176d2 from Jan 19th - didn't show
>> this problem. Want me to try and bisect further?
>
> Yes, please.
>
ee6fc514f2df821c2719cc49499a56ef2fb136b0 (Show submodules as modified
when they contain a dirty work tree) seems to be the first bad commit.
next prev parent reply other threads:[~2010-01-30 0:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 15:12 v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash Jonathan del Strother
[not found] ` <7vzl3wiz59.fsf@alter.siamese.dyndns.org>
2010-01-30 0:46 ` Jonathan del Strother [this message]
2010-01-30 12:31 ` Jens Lehmann
2010-01-30 13:23 ` Jonathan del Strother
2010-01-30 14:10 ` Jens Lehmann
2010-01-30 16:36 ` Jonathan del Strother
2010-01-30 20:01 ` Junio C Hamano
2010-01-30 20:25 ` Junio C Hamano
2010-01-30 20:30 ` [PATCH] is_submodule_modified(): fix breakage with external GIT_INDEX_FILE Junio C Hamano
2010-01-31 19:16 ` v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash Jonathan del Strother
2010-01-31 19:21 ` Jonathan del Strother
2010-01-31 19:21 ` Junio C Hamano
2010-01-30 20:44 ` Jens Lehmann
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=57518fd11001291646l5b0b581dm553689232b0910e8@mail.gmail.com \
--to=maillist@steelskies.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).