bug#42358: mv w/mkdir -p of destination

[Paul Eggert]

On 7/14/20 3:36 PM, L A Walsh wrote:

But I've found asking for features usually doesn't work and sometimes
results in work to preclude future
implementation of the feature.  Reporting bugs also, often gets ignored
until some large company reports
the same problem or until it causes a serious enough security incident.


You've often disagreed with design decisions made by maintainers, but this is 
the first time I recall you've accused them of large-company bias. Perhaps you 
should get your other grievances off your chest while you're at it.


I haven't noticed any such bias myself. Anyway, it does help to propose good 
patches, since my volunteer time is limited.

bug#42358: mv w/mkdir -p of destination

[L A Walsh]

Yeah, I'd thought about asking for this as well, like as maybe a "rmdir -r"
or rmdir -rp
where either the want of recursion implied going up to ancestors (since
decending along a chain
of directories would be a bit indeterminent, or requiring a redundant '-p',
as well, as it would tell the program to delete parents (since going down
wouldnt' make much since) from the dir specified back up to the current
directory.  If the current directory wasn't 'above' the specified dir, then
it would die
as it isn't clear what is wanted.  Obviously it can only follow a chain
'up' as long as nothing else is
in the parent besides the directory-parent (i.e. no other files or dirs).

But I've found asking for features usually doesn't work and sometimes
results in work to preclude future
implementation of the feature.  Reporting bugs also, often gets ignored
until some large company reports
the same problem or until it causes a serious enough security incident.

On Sun, May 10, 2020 at 8:17 PM Vito Caputo  wrote:

>
> Does this already exist?
>
> Was just moving a .tgz into a deep path and realized I hadn't created
> it on that host, and lamented not knowing what convenient flag I could
> toss on the end of the typed command to make `mv` do the mkdir -p
> first for me.
>
> I was surprised to not see it in mv --help or mv(1) when I checked for
> next time...
>
> Regards,
> Vito Caputo
>
>