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: AS54825 147.75.192.0/21 X-Spam-Status: No, score=-3.4 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org [147.75.199.223]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 2A49B1F406 for ; Fri, 8 Dec 2023 22:29:57 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=ttaylorr-com.20230601.gappssmtp.com header.i=@ttaylorr-com.20230601.gappssmtp.com header.a=rsa-sha256 header.s=20230601 header.b=u+y4MoGH; dkim-atps=neutral Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 752C61C20B30 for ; Fri, 8 Dec 2023 22:29:56 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 881E15A0E4; Fri, 8 Dec 2023 22:29:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=ttaylorr-com.20230601.gappssmtp.com header.i=@ttaylorr-com.20230601.gappssmtp.com header.b="u+y4MoGH" Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8EECE85 for ; Fri, 8 Dec 2023 14:29:43 -0800 (PST) Received: by mail-qk1-x72b.google.com with SMTP id af79cd13be357-77f42ee9370so101840785a.2 for ; Fri, 08 Dec 2023 14:29:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ttaylorr-com.20230601.gappssmtp.com; s=20230601; t=1702074582; x=1702679382; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=AhboHkyvfXeuYNbms7U7UbankdF9fTtNwcAMA2jHUJc=; b=u+y4MoGHuQ+wyWuN4nOYuKfkWYBtQtOmR5ZiMh/3oPuGtruMqK+Rfaj0rJZqQN9gcY grJFiKqaMvLynLKd8j9C6tBRuLGL3kacCPaH5a+nN1D+uvcXUWpBL28tbhf4342lMFnZ zbIgf+4k0cHak8oaFFoTLSkdVWQtwcgR2QIYPQEqosgFaOO7sCckF+P3S4QGQ7eQFVaL coNhqc+3hY3ZzQzXzq2xwpJr6AlyZqs/uTL+BH2+t6F0aediaWVve7zBpJeKXvbzJteh 3TF6rDK86Qw425L1s7Li7mZaSfitnCNxcJnPXF/dJuojFYyd9qRlmEl/sDpG1XQVscKP CpIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702074582; x=1702679382; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=AhboHkyvfXeuYNbms7U7UbankdF9fTtNwcAMA2jHUJc=; b=cFPoujBOE0xzaj8TLIc1S+rMeqZqgjOnZCwS+NmTfBmr1zZNFlylGz1egUTZhvN+W8 gkaInN2C1zJ5mTQD8lkPnfUFfy+DHjk2SIkqyU7ny2j/TBpXtp/9gF6hsdLyR659RI04 6Qq/2mAO0DobW2HlixyA2bou22suH4LweC8vBdkILISPB8DTZZIejK4KOgh6eMjyM7iD hCFucBi4PSn63aOGYBjvMJvrtKjW6jpYMpk5JGTxSNmQw9Q2O2dYTtFTUy1KVWAciOCm daCXnkgN8tAD+69oNT9bfrQqydlD1E/VfToKEM/RzldZnSRs8fHzewFy0SyoOBNanvx+ CugQ== X-Gm-Message-State: AOJu0Yyd989MZ7iCTdTjBxWfxnMArNxSKF/JuGMqj0WdygMcOnOtEVg2 UEQSaJ6ZUmFPmG9vuNu77OKgZA== X-Google-Smtp-Source: AGHT+IEYAcDO71Gh/+Boj2p7jH6TLOiryWRUwVdQsg1jFpAyoJ3GtNyVosXGN92PHnzwUAxaDRpHWw== X-Received: by 2002:a05:620a:530f:b0:77e:fba4:3a10 with SMTP id oo15-20020a05620a530f00b0077efba43a10mr769231qkn.102.1702074582695; Fri, 08 Dec 2023 14:29:42 -0800 (PST) Received: from localhost (104-178-186-189.lightspeed.milwwi.sbcglobal.net. [104.178.186.189]) by smtp.gmail.com with ESMTPSA id s8-20020a05620a080800b0077d742fb27esm998850qks.49.2023.12.08.14.29.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 08 Dec 2023 14:29:42 -0800 (PST) Date: Fri, 8 Dec 2023 17:29:41 -0500 From: Taylor Blau To: Junio C Hamano Cc: Jeff King , Vito Caputo , git@vger.kernel.org Subject: Re: Minor UX annoyance w/`git add --patch untracked/file` Message-ID: References: <20231130192637.wqpmidfv2roqmxdx@shells.gnugeneration.com> <20231206195407.GD103708@coredump.intra.peff.net> Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: On Sat, Dec 09, 2023 at 06:09:46AM +0900, Junio C Hamano wrote: > Jeff King writes: > > > They _could_, but keep in mind that the argument is not strictly a path. > > It is a pathspec that may match multiple paths. So: > > > > git add -p path/to/ > > > > for example will pick up the tracked files in path/to/, but not your > > untracked one. > > The corresponding command w/o "-p", i.e., "git add path/to/", will > pick up both tracked and untracked ones from the named directory, > while honoring the ignore settings. So I suspect it might feel more > natural if "-p" followed suit. I tend to agree. I do think that the full specification of when "git add -p" implies "git add -N ... && git add -p" would be difficult to explain to users. But I think it's a worthwhile trade-off in that it makes the UX more consistent in the common case (where the argument to add is a literal path, not a pathspec). Thanks, Taylor