Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Mar 11, 2009
  1. @j6t

    recv_sideband: Bands #2 and #3 always go to stderr

    j6t authored committed
    This removes the last parameter of recv_sideband, by which the callers
    told which channel bands #2 and #3 should be written to.
    Sayeth Shawn Pearce:
       The definition of the streams in the current sideband protocol
       are rather well defined for the one protocol that uses it,
         stream #1:  pack data
         stream #2:  stderr messages, progress, meant for tty
         stream #3:  abort message, remote is dead, goodbye!
    Since both callers of the function passed 2 for the parameter, we hereby
    remove it and send bands #2 and #3 to stderr explicitly using fprintf.
    This has the nice side-effect that these two streams pass through our
    ANSI emulation layer on Windows.
    Signed-off-by: Johannes Sixt <>
    Acked-by: Nicolas Pitre <>
    Signed-off-by: Junio C Hamano <>
Commits on Oct 11, 2006
  1. atomic write for sideband remote messages

    Nicolas Pitre authored Junio C Hamano committed
    It has been a few times that I ended up with such a confusing display:
    |remote: Generating pack...
    |remote: Done counting 17 objects.
    |remote: Result has 9 objects.
    |remote: Deltifying 9 objects.
    |remote:  100% (9/9) done
    |remote: Unpacking 9 objects
    |Total 9, written 9 (delta 8), reused 0 (delta 0)
    | 100% (9/9) done
    The confusion can be avoided in most cases by writing the remote message
    in one go to prevent interleacing with local messages.  The buffer
    declaration has been moved inside recv_sideband() to avoid extra string
    Signed-off-by: Nicolas Pitre <>
    Signed-off-by: Junio C Hamano <>
Commits on Sep 10, 2006
  1. Prepare larger packet buffer for upload-pack protocol.

    Junio C Hamano authored
    The original side-band support added to the upload-pack protocol used the
    default 1000-byte packet length.  The pkt-line format allows up to 64k, so
    prepare the receiver for the maximum size, and have the uploader and
    downloader negotiate if larger packet length is allowed.
    Signed-off-by: Junio C Hamano <>
  2. Move sideband server side support into reusable form.

    Junio C Hamano authored
    The server side support; this is just the very low level, and the
    caller needs to know which band it wants to send things out.
    Signed-off-by: Junio C Hamano <>
    (cherry picked from b786552b67878c7780c50def4c069d46dc54efbe commit)
  3. Move sideband client side support into reusable form.

    Junio C Hamano authored
    This moves the receiver side of the sideband support from
    fetch-clone.c to sideband.c and its header file, so that
    archiver protocol can use it.
    Signed-off-by: Junio C Hamano <>
Something went wrong with that request. Please try again.