Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
liblongpath-rsync
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
liblongpath
liblongpath-rsync
Commits
d1e77264
Commit
d1e77264
authored
Feb 14, 2004
by
J.W. Schultz
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove "Conditional -z for old protocols" because those old
protocols are no longer supported.
parent
0596df00
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
16 deletions
+0
-16
TODO
TODO
+0
-16
No files found.
TODO
View file @
d1e77264
...
@@ -16,7 +16,6 @@ Handling IPv6 on old machines
...
@@ -16,7 +16,6 @@ Handling IPv6 on old machines
Other IPv6 stuff:
Other IPv6 stuff:
Add ACL support 2001/12/02
Add ACL support 2001/12/02
Lazy directory creation
Lazy directory creation
Conditional -z for old protocols
proxy authentication 2002/01/23
proxy authentication 2002/01/23
SOCKS 2002/01/23
SOCKS 2002/01/23
FAT support
FAT support
...
@@ -255,21 +254,6 @@ Lazy directory creation
...
@@ -255,21 +254,6 @@ Lazy directory creation
-- --
-- --
Conditional -z for old protocols
After we get the @RSYNCD greeting from the server, we know it's
version but we have not yet sent the command line, so we could just
remove the -z option if the server is too old.
For ssh invocation it's not so simple, because we actually use the
command line to start the remote process. However, we only actually
do compression in token.c, and we could therefore once we discover
the remote version emit an error if it's too old. I'm not sure if
that's a good tradeoff or not.
-- --
proxy authentication 2002/01/23
proxy authentication 2002/01/23
Allow RSYNC_PROXY to be http://user:pass@proxy.foo:3128/, and do
Allow RSYNC_PROXY to be http://user:pass@proxy.foo:3128/, and do
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment