Date: Mon, 17 Oct 2016 19:38:41 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: freebsd-questions@freebsd.org Subject: Re: A request for cp flag Message-ID: <20161017193841.36b3df93ebd7ce0a32f4ef9e@sohara.org> In-Reply-To: <122eea3e-08a6-69a0-d67f-93873df095a6@FreeBSD.org> References: <VI1PR02MB0974F08FABD625DE9C2472B8F6D00@VI1PR02MB0974.eurprd02.prod.outlook.com> <122eea3e-08a6-69a0-d67f-93873df095a6@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Oct 2016 15:59:10 +0100 Matthew Seaman <matthew@FreeBSD.org> wrote: > You're not going to get anyone to change the behaviour of a core command > like cp(1) I'm afraid. For all that you dislike the behaviour when > copying a directory path that ends in '/' there will be many, many more > people that have written scripts that depend on that exact behaviour and > will be exceedingly peeved if those scripts stop working. Adding a -r flag wouldn't break anything at least until POSIX adds one that does something else and then there'd be a decision to make, for that reason I doubt anyone would entertain a new single letter option to cp. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161017193841.36b3df93ebd7ce0a32f4ef9e>