From: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>
To: Git List <git@vger.kernel.org>
Subject: Re: [Bug] git show crashes with deepened shallow clone
Date: Wed, 25 Sep 2013 17:10:08 +0200 [thread overview]
Message-ID: <5242FCD0.8050900@atlas-elektronik.com> (raw)
In-Reply-To: <5242F78C.5060607@atlas-elektronik.com>
Am 25.09.2013 16:47, schrieb Stefan Näwe:
> Just a quick report since I don't have time to bisect now (will do later
> if no other gitster is faster...)
Seems to be somewhere between v1.8.3.1 (OK) and v1.8.3.2 (not OK) !!
>
> When I execute the below script 'git show' crashes. 'git log --oneline -2' gives
> for example:
>
> 3808bade5b76c4663ac4a3f751dc9f1ed0b08f2e three
> error: Could not read 1e8777edeb2b7e757f74c789e679fc6c71073897
> fatal: Failed to traverse parents of commit 0aa4ef86004f5bb29f67e971d7963f5cf430c668
>
> gdb backtrace of one run is attached.
> It happens on 32-bit Debian (5.0.10), 64-bit openSUSE (12.2), and Windows XP with git 1.8.4
> on all systems.
>
> The help of 'git fetch' says:
>
> --depth=<depth>
>
> Deepen or shorten the history of a shallow repository created by git clone with
> --depth=<depth> option (see git-clone(1)) to the specified number of commits from
> the tip of each remote branch history. Tags for the deepened commits are not fetched.
> -------------------------------------------------------------------------------^^^^^^^^^
>
> But that's not true. The tag 'two' (from the script below) gets fetched when
> deepening the repository.
v1.8.3.1 fetches the tag also.
Stefan
--
----------------------------------------------------------------
/dev/random says: Pobody's Nerfect!
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"
next prev parent reply other threads:[~2013-09-25 15:10 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 [this message]
2013-09-25 15:27 ` Stefan Näwe
2013-09-25 18:08 ` Stefan Näwe
2013-09-25 18:48 ` Jonathan Nieder
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=5242FCD0.8050900@atlas-elektronik.com \
--to=stefan.naewe@atlas-elektronik.com \
--cc=git@vger.kernel.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).