GNU bug report logs - #20094
cp: add --dry-run option

Previous Next

Package: coreutils;

Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>

Date: Thu, 12 Mar 2015 03:32:01 UTC

Severity: wishlist

Tags: wontfix

Done: Assaf Gordon <assafgordon <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Bob Proulx <bob <at> proulx.com>
Cc: P <at> draigBrady.com, 20094 <at> debbugs.gnu.org
Subject: bug#20094: cp --dry-run
Date: Sat, 14 Mar 2015 00:58:02 +0800
I am mainly talking about "Where will it copy/move these things anyway? I'd
like to be sure before I commit. From reading the man page I have a good
idea, but I'd like to see what the path names will look like first
without actually doing anything."

And as a bonus: "I'm pretty much sure I can successfully cp/mv entire
complicated tree A onto entire complicated tree B, but it would be great
to know before I get started if deep inside B there is something that
will cause some tiny part of the whole operation to fail."

So no, cp --attributes-only can't help. And yes, indeed I see I am
hoping that these rsync features will get added to cp and mv, and cpio
too. (Or maybe just on the man pages mention: for "--dry-run"
capabilities try rsync -n !.




This bug report was last modified 6 years and 210 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.