On Sat, Apr 20, 2013 at 8:05 PM, Michael Heemskerk
mheemsk...@atlassian.com wrote:
When the client sends a 'shallow' line for an object that the server does
not have, the server currently dies with the error: did not find object
for shallow obj-id. The client may have received the object from a
Duy Nguyen pclo...@gmail.com writes:
On Sat, Apr 20, 2013 at 8:05 PM, Michael Heemskerk
mheemsk...@atlassian.com wrote:
When the client sends a 'shallow' line for an object that the server does
not have, the server currently dies with the error: did not find object
for shallow obj-id. The
On Sun, Apr 21, 2013 at 6:51 AM, Junio C Hamano gits...@pobox.com wrote:
Duy Nguyen pclo...@gmail.com writes:
But the shallow list is also used to compute the updated boundary
(i.e. this client does not have a valid history behind these
commits)? When we know their current shallow boundary,
3 matches
Mail list logo
