All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Clone from shallow bundle bug
Date: Wed, 01 Apr 2015 08:53:30 -0400	[thread overview]
Message-ID: <551BEA4A.9050708@ubuntu.com> (raw)
In-Reply-To: <CACsJy8C0wMFiPw1thSWN-dPVW+9N=JXDsy_HFCj=Oyu2rf40eg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4/1/2015 5:55 AM, Duy Nguyen wrote:
> On Wed, Apr 1, 2015 at 4:10 AM, Phillip Susi <psusi@ubuntu.com>
> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> I made a shallow clone of my repo, then used git bundle create to
>> pack it all into a bundle file, then cloned from that bundle.
>> The initial shallow clone has a .git/shallow file that identifies
>> it as a shallow clone ( and I guess keeps things from complaining
>> about the missing history ), but the the repo cloned from the
>> bundle does not,
> 
> You made me worry a bit. We have checks in clone and fetch to make 
> sure the result is "good" (i.e. gitk should not complain,
> clone/fetch should report it instead). Unfortunately I tested and
> it seemed to work as expected (i.e. clone fails)
> 
> $ LANG=C ./git clone ./shallow.bundle  shallow2 Cloning into
> 'shallow2'... Receiving objects: 100% (2813/2813), 5.33 MiB | 0
> bytes/s, done. Resolving deltas: 100% (250/250), done. Checking
> connectivity... error: Could not read 
> 50a3ba22454e2989424d5de489de9c0f68fed5ec fatal: Failed to traverse
> parents of commit c73a8a63134734ddf7077d09355a10a0077ed2ca fatal:
> remote did not send all necessary objects

Strange; it works fine for me using git 1.9.4.msysgit.1, and then I
just get the complaints from gitk.  I created the bundle with no
prereq argument, i.e. "git bundle create shallow.bundle".  Did you use
a prereq argument?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJVG+pKAAoJENRVrw2cjl5RLkMH/j0IlFsf5oEsFejLqD2fxFAJ
8r7pZCtYFvFqMqLQivLCdU/aYCd/5F99VUtusH3NphJvxkmCaLyRwLyA1KR/AozQ
slEXc5gmjbUg9yEBffYQ/xFPAGrizb2BblSzl6hcAZGtscLNyKvOjHttvJL+xM1+
uY0dwHcQ97m5p3DlehjLSAHolJF+waEhS6MarACZuSbi2JBTvo3OOagyt0o46sjp
t5v4kfRfTYD6DTlY+VPTUC56unBaVItLDfxY5d+iHGDY2o5rhl4AFWLbCh3v6ltl
OAuVs+UPKn0kV9tIQ6EBhQKf5CooCZtbr45OVGpVLPipjQFq2QqUjVWrLMEskhw=
=Fem/
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-04-01 12:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 21:10 Clone from shallow bundle bug Phillip Susi
2015-03-31 22:17 ` Junio C Hamano
2015-04-01  2:56   ` Phillip Susi
2015-04-01  6:31     ` Junio C Hamano
2015-04-01 10:01       ` Duy Nguyen
2015-04-01 13:00         ` Phillip Susi
2015-04-01 17:20         ` Junio C Hamano
2015-04-02  0:33           ` Duy Nguyen
2015-04-02  0:35             ` Duy Nguyen
2015-04-02  1:26             ` Phillip Susi
2015-04-01  9:55 ` Duy Nguyen
2015-04-01 12:53   ` Phillip Susi [this message]
2015-04-01 13:09     ` Duy Nguyen
2015-04-01 13:30       ` Phillip Susi
2015-04-01 13:36         ` Duy Nguyen
2015-04-01 14:06           ` Phillip Susi

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=551BEA4A.9050708@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@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 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.