Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-n and -v give very similar (read: the same) output #23

Closed
hashhar opened this issue Nov 17, 2015 · 2 comments
Closed

-n and -v give very similar (read: the same) output #23

hashhar opened this issue Nov 17, 2015 · 2 comments

Comments

@hashhar
Copy link
Collaborator

hashhar commented Nov 17, 2015

snip_20151118000427

Both -n and -v options give similarly formatted output... I think we should add a header like: "Operations that would have been performed:" to the -n option.

@laurent22
Copy link
Owner

I've probably implemented it that way based on the output of commands like rsync, which also don't indicate that they are running in dry run mode:

$ rsync -aP -n temp/ temp.test/
sending incremental file list
created directory temp.test
./
1.txt
2.txt
3.txt

I think it makes sense because you want to know exactly what would happen in dry-run mode, including what output would be generated (for example, if it's parsed by other tools). If we add a header the dry-run and regular mode will have different outputs and that could be a problem. So unless there's a good reason for it, I'd rather leave it as it is.

@hashhar
Copy link
Collaborator Author

hashhar commented Nov 17, 2015

Makes sense.

@hashhar hashhar closed this as completed Nov 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants