From: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
To: "Ricardo C" <rpc01234@gmail.com>
Cc: "Phillip Wood" <phillip.wood123@gmail.com>,
git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH] builtin/stash: configs keepIndex, includeUntracked
Date: Tue, 20 Feb 2024 20:30:03 +0100 [thread overview]
Message-ID: <14a10788-37fb-46ad-91f4-303703dbd312@app.fastmail.com> (raw)
In-Reply-To: <31135b8a-af7a-4d73-b3b3-d91ea8d3d5fd@gmail.com>
On Tue, Feb 20, 2024, at 04:59, Ricardo C wrote:
> That makes sense. Do you have any ideas on how to address this? It feels to me
> like providing this config option is fundamentally incompatible with requiring
> backwards-compatible behavior regardless of configuration.
If my armchair also had a time machine: one could have used an `-s`
option to `git` (`git -s stash`) that only reads a few configuration
variables, like `user.name` and `user.email`. It would read none of the
variables meant for making interactive/custom use convenient. This would
be meant for scripts. That way new user-convenience config variables
wouldn’t interfere with some `git -s` invocation deep in some script
somewhere.
As for the status quo though one seems stuck.
next prev parent reply other threads:[~2024-02-20 19:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 3:30 [PATCH] builtin/stash: configs keepIndex, includeUntracked MithicSpirit
2024-02-18 10:32 ` Phillip Wood
2024-02-18 17:54 ` Ricardo C
2024-02-20 11:01 ` Phillip Wood
2024-02-20 17:47 ` Junio C Hamano
2024-02-21 19:13 ` Ricardo C
2024-02-21 20:09 ` Junio C Hamano
2024-02-21 23:14 ` Ricardo C
2024-02-21 23:53 ` Junio C Hamano
2024-02-20 2:52 ` Junio C Hamano
2024-02-20 3:30 ` Ricardo C
2024-02-20 3:44 ` Junio C Hamano
2024-02-20 3:59 ` Ricardo C
2024-02-20 19:30 ` Kristoffer Haugsbakk [this message]
2024-02-19 8:04 ` Jean-Noël Avila
2024-02-19 21:41 ` Ricardo C
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14a10788-37fb-46ad-91f4-303703dbd312@app.fastmail.com \
--to=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood123@gmail.com \
--cc=rpc01234@gmail.com \
/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 NNTP newsgroup(s).