On Mon, Jul 15, 2013 at 8:01 AM, Duy Nguyen pclo...@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
Duy Nguyen pclo...@gmail.com writes:
On Mon, Jul 15, 2013 at 8:01 AM, Duy Nguyen pclo...@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
Duy Nguyen pclo...@gmail.com writes:
On Sun, Jul 14, 2013 at 4:25 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Hi,
Nguyễn Thái Ngọc Duy wrote:
Since 52fed6e (receive-pack: check connectivity before concluding git
push - 2011-09-02), receive-pack is prepared to deal with broken
push, a
On Mon, Jul 15, 2013 at 1:52 AM, Junio C Hamano gits...@pobox.com wrote:
Duy Nguyen pclo...@gmail.com writes:
On Sun, Jul 14, 2013 at 4:25 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Hi,
Nguyễn Thái Ngọc Duy wrote:
Since 52fed6e (receive-pack: check connectivity before concluding git
Hi,
Nguyễn Thái Ngọc Duy wrote:
Since 52fed6e (receive-pack: check connectivity before concluding git
push - 2011-09-02), receive-pack is prepared to deal with broken
push, a shallow push can't cause any corruption. Update the document
to reflect that.
Hmm, what happens when pushing to
On Sun, Jul 14, 2013 at 4:25 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Hi,
Nguyễn Thái Ngọc Duy wrote:
Since 52fed6e (receive-pack: check connectivity before concluding git
push - 2011-09-02), receive-pack is prepared to deal with broken
push, a shallow push can't cause any corruption.
On Fri, Jul 12, 2013 at 12:54 PM, Junio C Hamano gits...@pobox.com wrote:
Nguyễn Thái Ngọc Duy pclo...@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
The document says one cannot push from a shallow clone. But that is
not true (maybe it was at some point in the past). The client does not
stop such a push nor does it give any indication to the receiver that
this is a shallow push. If the receiver accepts it, it's in.
Since 52fed6e
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
The document says one cannot push from a shallow clone. But that is
not true (maybe it was at some point in the past). The client does not
stop such a push nor does it give any indication to the receiver that
this is a shallow push. If the
Nguyễn Thái Ngọc Duy pclo...@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
10 matches
Mail list logo