From: Ralph Seichter <git-ml@seichter.de>
To: "Carlos Martín Nieto" <cmn@elego.de>
Cc: git@vger.kernel.org
Subject: Re: How to limit bandwidth used by git over SSH ?
Date: Wed, 20 Jul 2011 21:18:56 +0200 [thread overview]
Message-ID: <4E272A20.8080904@seichter.de> (raw)
In-Reply-To: <1311064940.3945.11.camel@bee.lab.cmartin.tk>
On 19.07.11 10:42, Carlos Martín Nieto wrote:
> There is a tool called trickle which takes over the network functions
> and can be used to limit upload and download speeds [...]
Thanks for the hint, Carlos. I tried to compile trickle on OS X 10.6.8,
but without success. AFAIK, trickle has not been tested with OS X, and I
am not even sure it trickle could work at all. Members of the MacPorts
mailing list seem to confirm my suspicion. I've tried to contact the
author of trickle; hopefully he will reply.
The general idea to use a tool besides git or SSH to shape the bandwidth
usage seems valid, though.
-Ralph
next prev parent reply other threads:[~2011-07-20 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 10:22 How to limit bandwidth used by git over SSH ? Ralph Seichter
2011-07-19 8:42 ` Carlos Martín Nieto
2011-07-20 19:18 ` Ralph Seichter [this message]
2011-07-20 20:20 ` Andreas Krey
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=4E272A20.8080904@seichter.de \
--to=git-ml@seichter.de \
--cc=cmn@elego.de \
--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).