Duy Nguyen <pclo...@gmail.com> writes:
> On Sun, Jul 14, 2013 at 4:25 AM, Jonathan Nieder <jrnie...@gmail.com> wrote:
>> 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 servers without that commit? Do you
>> think it should be applied to Debian squeeze for server operators that
>> haven't upgraded yet to the current stable release?
> This is pushing _from_ a shallow repo, where the sender repo's old
> objects is a subset of the receiver's.
The "subset" assumption does not necessarily hold, does it? The
receiver may have rewound its tips and pruned since then.
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.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html