All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-clone.txt: remove the restriction on pushing from a shallow clone
Date: Mon, 15 Jul 2013 13:33:49 +0700	[thread overview]
Message-ID: <CACsJy8DELmhBwBCk9hmg4EpQxGeCRDPaSEr5rYp=CiMjq8j54Q@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8Bx_o+9S1N_uieQaV8NBbc3T_MR_VCvF+fM==Dy-vt7tw@mail.gmail.com>

On Mon, Jul 15, 2013 at 8:01 AM, Duy Nguyen <pclouds@gmail.com> wrote:
>> Also, the sender may have cloned from the receiver (fully) and then
>> fetched a different history shallowly from elsewhere.  The receiver
>> may have no commit on that history, including the shallow-bottom.
>>
>
> Hmm.. right. And the receiver needs to setup proper graft to seal the
> shallow bottom. So it's really not safe to do pushing from a shallow
> repo without 52fed6e

Because this makes pushing from a shallow repo fall into "mostly
works" category, I withdraw this patch.
--
Duy

  reply	other threads:[~2013-07-15  6:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  5:37 [PATCH] git-clone.txt: remove the restriction on pushing from a shallow clone Nguyễn Thái Ngọc Duy
2013-07-12  5:53 ` Junio C Hamano
2013-07-12  5:54 ` Junio C Hamano
2013-07-12  7:54   ` Duy Nguyen
2013-07-13 21:25 ` Jonathan Nieder
2013-07-14  2:28   ` Duy Nguyen
2013-07-14 18:52     ` Junio C Hamano
2013-07-15  1:01       ` Duy Nguyen
2013-07-15  6:33         ` Duy Nguyen [this message]
2013-07-15 15:31           ` Junio C Hamano
2013-07-15 15:35           ` [PATCH] Revert "git-clone.txt: remove the restriction on pushing from a shallow clone" Junio C Hamano

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='CACsJy8DELmhBwBCk9hmg4EpQxGeCRDPaSEr5rYp=CiMjq8j54Q@mail.gmail.com' \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@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.