From: Junio C Hamano <gitster@pobox.com>
To: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, dstolee@microsoft.com,
Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH v2 0/2] Sparse checkout status
Date: Thu, 18 Jun 2020 14:45:55 -0700 [thread overview]
Message-ID: <xmqqwo44kpyk.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <pull.808.v2.git.git.1592513398.gitgitgadget@gmail.com> (Elijah Newren via GitGitGadget's message of "Thu, 18 Jun 2020 20:49:56 +0000")
"Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com> writes:
> Some of the feedback of folks trying out sparse-checkouts at $dayjob is that
> sparse checkouts can sometimes be disorienting; users can forget that they
> had a sparse-checkout and then wonder where files went. This series adds
> some output to 'git status' and modifies git-prompt slightly as an attempt
> to help.
>
> Note that as per discussion on v1, we may want to later add a git
> sparse-checkout subcommand named something like 'stats' or 'info' or
> 'status' that provides more detailed information for users to dig deeper.
> That would be an additional improvement for helping users find out more
> information once they realize or remember they are in a sparse checkout,
> this is just aimed at giving them a simple reminder.
>
> Changes since v1:
>
> * Replaced the -1 magic constant with SPARSE_CHECKOUT_DISABLED
> * Fixed a possible division by 0 (when there are no entries in the index
> AND sparse checkout is enabled; not sure when that'd ever happen but
> still better to guard against...)
> * Slight wording tweaks for the git-prompt commit message
> * Removed the RFC label
>
> Elijah Newren (2):
> wt-status: show sparse checkout status as well
> git-prompt: include sparsity state as well
>
> contrib/completion/git-prompt.sh | 7 +++++-
> wt-status.c | 41 ++++++++++++++++++++++++++++++++
> wt-status.h | 2 ++
> 3 files changed, 49 insertions(+), 1 deletion(-)
Any change to Documentation/git-status.txt?
next prev parent reply other threads:[~2020-06-18 21:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 23:33 [PATCH 0/2] Sparse checkout status Elijah Newren via GitGitGadget
2020-06-16 23:33 ` [PATCH 1/2] [RFC] wt-status: show sparse checkout status as well Elijah Newren via GitGitGadget
2020-06-17 14:50 ` Derrick Stolee
2020-06-17 15:46 ` Elijah Newren
2020-06-16 23:33 ` [PATCH 2/2] [RFC] git-prompt: include sparsity state " Elijah Newren via GitGitGadget
2020-06-18 20:49 ` [PATCH v2 0/2] Sparse checkout status Elijah Newren via GitGitGadget
2020-06-18 20:49 ` [PATCH v2 1/2] wt-status: show sparse checkout status as well Elijah Newren via GitGitGadget
2020-06-18 20:49 ` [PATCH v2 2/2] git-prompt: include sparsity state " Elijah Newren via GitGitGadget
2020-06-19 16:15 ` SZEDER Gábor
2020-06-19 16:33 ` Junio C Hamano
2020-06-19 16:35 ` Junio C Hamano
2020-06-18 21:45 ` Junio C Hamano [this message]
2020-06-18 23:18 ` [PATCH v2 0/2] Sparse checkout status Elijah Newren
2020-06-21 1:34 ` Elijah Newren
2020-06-21 5:21 ` [PATCH v3 0/3] " Elijah Newren via GitGitGadget
2020-06-21 5:21 ` [PATCH v3 1/3] wt-status: show sparse checkout status as well Elijah Newren via GitGitGadget
2020-06-21 5:21 ` [PATCH v3 2/3] git-prompt: document how in-progress operations affect the prompt Elijah Newren via GitGitGadget
2020-06-21 5:21 ` [PATCH v3 3/3] git-prompt: include sparsity state as well Elijah Newren via GitGitGadget
2020-06-22 16:35 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2020-06-19 2:28 [PATCH v2 0/2] Sparse checkout status Russell Crume
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=xmqqwo44kpyk.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=newren@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).