"Cloned Uploads"

It would be nice if one could set a "Working Folder" in the settings of the ftp/scp-profile.
If you upload a new/modified file, the file should also be stored in the same location in the "Working Folder"

Example:
You are connected to "ftp.example.org" and had set the working-folder for "ftp.example.org" to "c:\somefolder\ftp.example.org\"
Now you modified "\somepath\sample.txt" on the ftp and winscp reuploads the file. At the same time "c:\somefolder\ftp.example.org\somepath\sample.txt" should be created/updated.

Why is this useful?
"c:\somefolder\ftp.example.org\" could be an svn-folder and one could keep track of the changes made on the ftp :D

bluppdidupp wrote:

Now you modified "\somepath\sample.txt" on the ftp and winscp reuploads the file.

I'm lost. Why should WinSCP upload a file when a remote file is changed?

I meant that in WinSCP the remote file '\somepath\sample.txt' was openend using "Edit", which downloads sample.txt to C:\Users\..\AppData\Local\Temp\scpXXX\..\sample.txt and opens it in an editor and reuploads the file when it changes.

The "Working Folder" would be linked to the actions that WinSCP does on the remote site:

If {workingdir} is under SVN control, i could see what files i changed/added/deleted since the last commit (and file diffs).

Another usage: You manage a website live.example.org, but changes are first done in an exact copy 'dev.example.org'.
1) You clear {workingdir}
2) You do some changes on dev.example.org (which was linked to {workingdir})
3) When you are done, all touched/modified/new files are in the {workingdir} and could now directly be copied to live.example.org - No need to manually track changes and redo them manually in live.example.org

I hope this explanation does not make it even more incomprehensible :D

OK, thanks for your explanation. Let's see if more people ask for this.