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 09:30:14 -0400 [thread overview]
Message-ID: <551BF2E6.6050000@ubuntu.com> (raw)
In-Reply-To: <CACsJy8C4G01LOhg13=rhkCTMGTq-NTHgG-k-kaoT9jALnd7CZw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 4/1/2015 9:09 AM, Duy Nguyen wrote:
>> 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?
>
> No, just your command plus a branch name. I tried v1.9.4.msysgit.1
> (but on linux, not windows), clone rejected too.
Even stranger... when I use a branch name, the clone fails, but not
when I use a detached HEAD.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJVG/LlAAoJENRVrw2cjl5RKtQH/2TTJ31PtG+3MQjlKjyMhhNZ
Xl/A7QSvruDEUF8V7kdyCYlN4I3EQIelMHeG0tZPWw/qnOPMMvpMvxI2xu3na0xf
L4AopC3XPFCe2kRG4EV17Nf0QAR8zx+ARGhCzf+PzLgGlFdmMsN3TZ/8Oe3yJHSZ
/eu+CPvmvE0N5PeC1EnPoYJwoTcBHFFI5he736OHI5PA8WtekJPQ2SZ17pZttN0p
jmZSeqoUZAe4Jeu+xfE0hYuuoVKtlkat/2GmOKrYcglyuw1+RaU31op+mKkhtGyw
x8yq0LmJ+zMAtj3Ab5fqv0rRrjbNPYeO5uTT+lgHSU62QRPVclv8lkugRyotcMk=
=owOK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-04-01 13:31 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
2015-04-01 13:09 ` Duy Nguyen
2015-04-01 13:30 ` Phillip Susi [this message]
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=551BF2E6.6050000@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.