From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: [PATCH RESEND 0/6] Sideband support in push (send-pack/receive-pack)
Date: Thu, 14 Feb 2008 01:22:02 -0500 [thread overview]
Message-ID: <20080214062202.GI24004@spearce.org> (raw)
This series adds the same sort of sideband channel we use in fetch
(fetch-pack/upload-pack) to pass progress messages back to the
client from the server side.
1) Allow run_command stdout_to_stderr when stderr is a pipe
2) Automatically close stderr pipes created by run_command
3) Refactor packet_write to prepare to integrate with sideband
4) Refactor send-pack/receive-pack capability handshake for extension
5) Add side-band-64k extension to send-pack/receive-pack for hook output
6) Redirect receive-pack hook output into sideband channel
I didn't really see any comments from the list on this topic the
last time I posted it for comment, so here is a rebased version
on current master.
--
Shawn.
reply other threads:[~2008-02-14 6:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080214062202.GI24004@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).