From: Ricardo C <rpc01234@gmail.com>
To: git@vger.kernel.org
Subject: Interest in options for stash -k and -u by default
Date: Wed, 7 Feb 2024 15:59:54 -0500 [thread overview]
Message-ID: <3470180e-2ef7-4393-9d32-92cd419727f5@gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1220 bytes --]
Hello,
After some discussion on Mastodon[1], I decided to try my hand at creating
configuration options that enable --keep-index and --include-untracked in
git-stash by default. I have made a preliminary such patch[2], and some
additional discussion[3] has encouraged me to try submitting it upstream.
I am wondering whether this change is something that would even be considered
for being accepted. The patch still needs some work (mainly documentation and
tests), which I'd be happy to do if I knew there was upstream interest in this
work.
I would also appreciate feedback on the patch. Currently, it creates two
separate options: stash.keepindex and stash.includeuntracked. These options
set the default value of --keep-index and --include-untracked if not otherwise
specified (e.g., --no-keep-index) and do not conflict with other options
(e.g., --patch). More details are of course available in the source code[2].
Thank you,
Ricardo "MithicSpirit" Prado Cunha
[1] https://bsd.network/@ed1conf/111783574839749798
[2]
https://github.com/MithicSpirit/git/commit/f33c8d5d26d8438ddb123781bd5db3bff8618247.patch
[3] https://social.jvns.ca/@b0rk/111880230506448122
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3215 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2024-02-07 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 20:59 Ricardo C [this message]
2024-02-07 21:08 ` Interest in options for stash -k and -u by default Junio C Hamano
2024-02-07 21:42 ` Kristoffer Haugsbakk
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=3470180e-2ef7-4393-9d32-92cd419727f5@gmail.com \
--to=rpc01234@gmail.com \
--cc=git@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