From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Karel Zak <kzak@redhat.com>
Cc: "Petr Malat" <oss@malat.biz>,
util-linux <util-linux@vger.kernel.org>,
"Paul Eggert" <eggert@cs.ucla.edu>,
"Dominique Martinet" <asmadeus@codewreck.org>,
69532@debbugs.gnu.org, "Rob Landley" <rob@landley.net>,
"Pádraig Brady" <P@draigBrady.com>
Subject: bug#69532: mv's new -x option should be made orthogonal to -t/-T/default
Date: Sat, 23 Mar 2024 11:24:18 +0100 [thread overview]
Message-ID: <9bbddfd0-d4a6-40f8-8ec3-bdbdecbc16ba@bernhard-voelker.de> (raw)
In-Reply-To: <20240322102257.ovv5kpnm4zsgtf7n@ws.net.home>
On 3/22/24 11:22, Karel Zak wrote:
> On Wed, Mar 20, 2024 at 11:53:05PM +0100, Bernhard Voelker wrote:>> On userland OTOH, we have broader choice.
>> Karel did his choice in util-linux for exch(1), and coreutils could expose
>> the same functionality.
>>
>> For other feature requests, we were much more reluctant in coreutils ... for
>> good reasons: feature bloat, maintainability, etc.
>>
>> So I'm asking myself what is different this time?
>> - The feature already exists -> util-linux.
>
> Note that we can move exch(1) from util-linux to coreutils if, at the
> end of the brainstorming session, the conclusion will be that mv(1) is
> a bad choice :-)
I'd be for that as well, because ...
>> I'm currently only 20:80 for adding it to mv(1).
>
> I think the functionality will be lost in the mv(1) for many users.
... that's a fair point.
The code for the functionality is in copy.c, so - as with mv.c/cp.c/install.c -
we could have a exch.c using just that part, and thus expose a clearer interface
to the users.
Have a nice day,
Berny
next prev parent reply other threads:[~2024-03-23 10:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 0:44 bug#69532: mv's new -x option should be made orthogonal to -t/-T/default Paul Eggert
2024-03-04 15:47 ` Pádraig Brady
2024-03-04 20:35 ` Pádraig Brady
2024-03-04 23:16 ` Petr Malat
2024-03-05 0:08 ` Paul Eggert
2024-03-05 4:35 ` Paul Eggert
2024-03-05 0:43 ` Dominique Martinet
2024-03-05 2:24 ` Rob Landley
2024-03-05 4:10 ` Paul Eggert
2024-03-05 5:05 ` Dominique Martinet
2024-03-05 14:16 ` Pádraig Brady
2024-03-05 20:41 ` Karel Zak
2024-03-05 22:13 ` Masatake YAMATO
2024-03-17 6:10 ` Paul Eggert
2024-03-17 11:32 ` Pádraig Brady
2024-03-17 11:40 ` Pádraig Brady
2024-03-20 22:10 ` Paul Eggert
2024-03-20 19:43 ` Bernhard Voelker
2024-03-20 20:56 ` Paul Eggert
2024-03-20 22:53 ` Bernhard Voelker
2024-03-20 23:56 ` Paul Eggert
2024-03-21 21:45 ` Bernhard Voelker
2024-03-23 1:44 ` Paul Eggert
2024-03-23 10:24 ` Bernhard Voelker
2024-03-22 10:22 ` Karel Zak
2024-03-23 10:24 ` Bernhard Voelker [this message]
2024-03-21 0:03 ` Rob Landley
2024-03-04 23:37 ` Petr Malat
2024-03-05 0:24 ` Paul Eggert
2024-03-05 7:17 ` Petr Malat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9bbddfd0-d4a6-40f8-8ec3-bdbdecbc16ba@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=69532@debbugs.gnu.org \
--cc=P@draigBrady.com \
--cc=asmadeus@codewreck.org \
--cc=eggert@cs.ucla.edu \
--cc=kzak@redhat.com \
--cc=oss@malat.biz \
--cc=rob@landley.net \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).