Incorrect handling of source destination arguments in dsync
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 200
- Forks
- 85
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Description
dsync, and probably dcp, are handling source/destination arguments incorrectly.
Example:
source /a/b where b is a directory (with say /a/b/f being a file)
destination /c/.
dsync /a/b /c/.
results in the contents of /a/b being copied to /c resulting in /c/f, where as the correct behavior is that b is copied to c, with /c/b being the result.
I.e. dsync/dcp should adhere to how rsync/cp behaves.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the source/destination argument handling for dsync and dcp, then reproduce the /a/b to /c/. example from the issue. Compare the resulting paths with rsync or cp behavior; done means the directory is placed at /c/b rather than copying only its contents into /c.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100