![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Daniel Barkalow <barkalow@iabervon.org> | |
| Thu, 28 Feb 2008 16:10:51 +0000 (11:10 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 29 Feb 2008 08:00:29 +0000 (00:00 -0800) | ||
| commit | 00183cbb3d0f60852d7286e766c9b631c0c1f952 | |
| tree | a31935e519b6102f6cbf3abaf831340993b4ee31 | tree | snapshot |
| parent | 7435982102093179474a128648179a44042d8a1c | commit | diff |
Always use the current connection's remote ref list in git protocol
We always report to the user the list of refs we got from the first
connection, even if we do multiple connections. But we should always
use each connection's own list of refs in the communication with the
server, in case we got a different server out of DNS rotation or the
timing was surprising or something.
Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
We always report to the user the list of refs we got from the first
connection, even if we do multiple connections. But we should always
use each connection's own list of refs in the communication with the
server, in case we got a different server out of DNS rotation or the
timing was surprising or something.
Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| transport.c | diff | blob | history |