From: Jonathan Nieder <jrnieder@gmail.com>
To: "Stefan Näwe" <stefan.naewe@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Bug] git show crashes with deepened shallow clone
Date: Wed, 25 Sep 2013 11:48:51 -0700 [thread overview]
Message-ID: <20130925184851.GX9464@google.com> (raw)
In-Reply-To: <loom.20130925T200459-360@post.gmane.org>
Stefan Näwe wrote:
> Stefan Näwe <stefan.naewe <at> atlas-elektronik.com> writes:
>> 6035d6aad8ca11954c0d7821f6f3e7c047039c8f is the first bad commit
>
> And to answer myself once more:
>
> That's fixed in
>
> 6da8bdc fetch-pack: do not remove .git/shallow file when --depth is not specified"
>
> Sorry for all the noise.
No problem.
It's probably worth releasing 1.8.4.1 soon. Thanks for a reminder.
prev parent reply other threads:[~2013-09-25 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 14:47 [Bug] git show crashes with deepened shallow clone Stefan Näwe
2013-09-25 15:10 ` Stefan Näwe
2013-09-25 15:27 ` Stefan Näwe
2013-09-25 18:08 ` Stefan Näwe
2013-09-25 18:48 ` Jonathan Nieder [this message]
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=20130925184851.GX9464@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=stefan.naewe@gmail.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).