From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-clone.txt: remove the restriction on pushing from a shallow clone
Date: Fri, 12 Jul 2013 14:54:35 +0700 [thread overview]
Message-ID: <CACsJy8BnOtgeRrJL5D0HQALstqNzcppabRoE7bYGG37kYz+GeA@mail.gmail.com> (raw)
In-Reply-To: <7vy59cnx06.fsf@alter.siamese.dyndns.org>
On Fri, Jul 12, 2013 at 12:54 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Nguyễn Thái Ngọc Duy <pclouds@gmail.com> writes:
>
>> + number of limitations (you cannot clone or fetch from it, nor
>> + push into it), but is adequate if you are only interested in
>> + the recent history of a large project with a long history.
>
> Ahh, sorry for the noise. You still say you cannot push _into_ it.
Yes, I actually removed that check in the first iteration of this
patch, reasoning that it can't cause any harm and it mostly works. But
"mostly" is not good enough. I will try remove it later if I can make
it always work by extending git protocol a bit (I think full clone
pushing to shallow one can always work. Shallow pushing to shallow,
probably no such guarantee)
--
Duy
next prev parent reply other threads:[~2013-07-12 7:55 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 [this message]
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
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACsJy8BnOtgeRrJL5D0HQALstqNzcppabRoE7bYGG37kYz+GeA@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).