| commit | 3ccc7aadd27b6ac5e7b391fbda6494cdbc0acfbc | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 29 Jun 2008 07:59:23 +0000 (29 03:59 -0400) | ||
| committer | Robin Rosenberg <robin.rosenberg@dewire.com> | |
| Mon, 30 Jun 2008 22:46:22 +0000 (1 00:46 +0200) | ||
| tree | d85370f6340986fccdb3bbb165ebfa33dc3fb89e | treesnapshot (tar.gz zip) |
| parent | ca7bb929d73621abf7986dad08561258848ba10f | commitdiff |
Support push over the sftp:// dumb transport
jgit now allows users to push changes over the sftp:// protocol,
taking advantage of the SFTP client available as part of JSch to
(more or less) safely update the remote repository.
Since locking is not available over SFTP this is not suitable for
use with concurrent pushes, but is safe with concurrent fetches
during a single push. This is sufficient support to safely update
a Git repository published over HTTP where the only means of making
changes is through SSH/SFTP and the remote side does not make Git
available through the shell, or does not offer direct shell access.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
jgit now allows users to push changes over the sftp:// protocol,
taking advantage of the SFTP client available as part of JSch to
(more or less) safely update the remote repository.
Since locking is not available over SFTP this is not suitable for
use with concurrent pushes, but is safe with concurrent fetches
during a single push. This is sufficient support to safely update
a Git repository published over HTTP where the only means of making
changes is through SSH/SFTP and the remote side does not make Git
available through the shell, or does not offer direct shell access.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>