From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg@dewire.com>,
Marek Zawirski <marek.zawirski@gmail.com>
Cc: git@vger.kernel.org
Subject: [JGIT PATCH 0/5] Yet another round of transport fixes
Date: Thu, 10 Jul 2008 02:13:18 -0400 [thread overview]
Message-ID: <1215670403-19191-1-git-send-email-spearce@spearce.org> (raw)
Apparently tweaking minor details is never done. This short
series improves minor issues I have with the transport code
in relation to error and progress reporting. We also get a
small performance boost for tag fetching over SSH.
Shawn O. Pearce (5):
Include a progress meter for large uploads to Amazon S3
Don't display passwords on the console in fetch/push output
Reuse the same SSH connection when automatically fetching tags
Report remote SSH execution errors during push via TransportException
Explicitly capture the stderr from a failed SSH fetch or push
.../org/spearce/egit/core/op/CloneOperation.java | 10 ++-
.../spearce/egit/ui/EclipseSshSessionFactory.java | 5 +-
.../egit/ui/internal/clone/SourceBranchPage.java | 1 +
.../spearce/jgit/transport/PushProcessTest.java | 5 +
.../org/spearce/jgit/transport/TransportTest.java | 10 ++
.../jgit/errors/NoRemoteRepositoryException.java | 59 +++++++++++
.../src/org/spearce/jgit/pgm/Fetch.java | 19 +++--
.../src/org/spearce/jgit/pgm/LsRemote.java | 1 +
.../src/org/spearce/jgit/pgm/Push.java | 2 +-
.../src/org/spearce/jgit/transport/AmazonS3.java | 29 +++++-
.../spearce/jgit/transport/BasePackConnection.java | 3 +-
.../jgit/transport/DefaultSshSessionFactory.java | 30 ++++++-
.../src/org/spearce/jgit/transport/Transport.java | 10 ++
.../spearce/jgit/transport/TransportAmazonS3.java | 12 ++-
.../spearce/jgit/transport/TransportBundle.java | 5 +
.../spearce/jgit/transport/TransportGitAnon.java | 5 +
.../spearce/jgit/transport/TransportGitSsh.java | 103 +++++++++++++-------
.../org/spearce/jgit/transport/TransportHttp.java | 5 +
.../org/spearce/jgit/transport/TransportLocal.java | 5 +
.../org/spearce/jgit/transport/TransportSftp.java | 57 ++++++-----
.../spearce/jgit/transport/WalkPushConnection.java | 5 +-
.../jgit/transport/WalkRemoteObjectDatabase.java | 11 ++-
22 files changed, 303 insertions(+), 89 deletions(-)
create mode 100644 org.spearce.jgit/src/org/spearce/jgit/errors/NoRemoteRepositoryException.java
next reply other threads:[~2008-07-10 6:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 6:13 Shawn O. Pearce [this message]
2008-07-10 6:13 ` [JGIT PATCH 1/5] Include a progress meter for large uploads to Amazon S3 Shawn O. Pearce
2008-07-10 6:13 ` [JGIT PATCH 2/5] Don't display passwords on the console in fetch/push output Shawn O. Pearce
2008-07-10 6:13 ` [JGIT PATCH 3/5] Reuse the same SSH connection when automatically fetching tags Shawn O. Pearce
2008-07-10 6:13 ` [JGIT PATCH 4/5] Report remote SSH execution errors during push via TransportException Shawn O. Pearce
2008-07-10 6:13 ` [JGIT PATCH 5/5] Explicitly capture the stderr from a failed SSH fetch or push Shawn O. Pearce
2008-07-10 18:56 ` [JGIT PATCH 2/5] Don't display passwords on the console in fetch/push output Robin Rosenberg
2008-07-10 20:17 ` Robin Rosenberg
2008-07-10 22:25 ` Johannes Schindelin
2008-07-10 22:42 ` Robin Rosenberg
2008-07-11 3:20 ` Shawn O. Pearce
2008-07-11 8:30 ` Robin Rosenberg
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=1215670403-19191-1-git-send-email-spearce@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=marek.zawirski@gmail.com \
--cc=robin.rosenberg@dewire.com \
/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).