From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-1.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=no autolearn_force=no version=3.4.6 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 1388C1F454 for ; Tue, 10 Oct 2023 01:00:29 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=pobox.com header.i=@pobox.com header.a=rsa-sha256 header.s=sasl header.b=OR4nVAfH; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1379370AbjJJA7z (ORCPT ); Mon, 9 Oct 2023 20:59:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45896 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1379367AbjJJA7y (ORCPT ); Mon, 9 Oct 2023 20:59:54 -0400 Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A4348A6 for ; Mon, 9 Oct 2023 17:59:52 -0700 (PDT) Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 1AE731BDA61; Mon, 9 Oct 2023 20:59:52 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:in-reply-to:references:date:message-id:mime-version :content-type; s=sasl; bh=dWIR2kSFInkbREzF2rSkiVvtIumkhrRW2NcJtw GwqVk=; b=OR4nVAfHzMCOtDrcO69EdLCKPKhAv2Wmb2JFdbSJ2bal7vgzpwRlMb 5LQbDx2m65uTDBJYdHRvhSS8OJ9ACZcxUOfIQgfKsO7Q6x0Xgw9qyR61T/jbpgTm PgM9L3E3AGvcSqAHIsHgLiQPbjHD4tHEF59YZcEuTQZpjscvIQ9eo= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 130AA1BDA60; Mon, 9 Oct 2023 20:59:52 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.125.153.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 76B401BDA5F; Mon, 9 Oct 2023 20:59:51 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Hugo Sales Cc: git@vger.kernel.org, Shaoxuan Yuan Subject: Re: [PATCH 0/3] Add `-p' option to `git-mv', inspired by `mkdir' In-Reply-To: (Junio C. Hamano's message of "Mon, 09 Oct 2023 17:39:22 -0700") References: <20231009233458.1371351-1-hugo@hsal.es> Date: Mon, 09 Oct 2023 17:59:50 -0700 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 5137BDBE-6708-11EE-A077-78DCEB2EC81B-77302942!pb-smtp1.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Junio C Hamano writes: > Regardless of the "do we require, or is it sifficient to imply, the > '-p' option when we lack leading directories?" question, once we > start "auto-creating" the leading directory hierarchy, one worrysome > thing such a new feature introduces is an ambiguity and unexpected > behaviour. ... > Both are plausible, and "mkdir -p" does not have such a nasty > ambiguity. That is what makes me unsure about the new feature > (again, either with required "-p" or with implied "-p"). I checked what POSIX, who does give "-p" to mkdir(1), has with mv(1), and they do not have "-p". Neither GNU, which tends to add such "usability" enhancements on top of what everybody else has. And I think they are being very sensible. By not adding such an option to "mv", they can sidestep the unnecessary ambiguity, and it isn't too bad to do a "mkdir -p" separately before doing such a "mv" into a (potential) new directory. So, let's not do this patch. Thanks.