git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 0/2] Sparse checkout status

From
Elijah Newren <newren@gmail.com>
Date
Jun 18, 2020, 23:18 UTC
Message-ID
<CABPp-BHLDhRTpdjfrG5WLjwxkegC--RXrjzxV+ufYKnH+Kdifw@mail.gmail.com>
In-Reply-To
<xmqqwo44kpyk.fsf@gitster.c.googlers.com>
On Thu, Jun 18, 2020 at 2:46 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 35 quoted lines
>
> "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?

Reasonable question; I didn't think of it. But on a related note, in the eight years we've had status output for various other forms of state (in-progress operations like merge, cherry-pick, rebase, or bisect), these haven't been documented either. Was that also oversight, or was there a reason it was left out?

If oversight, should I just document all those others while I'm at it?
Previous: Junio C HamanoNext: Elijah Newren
Message 13 of 19 in “Sparse checkout status”
  1. 0/2 Sparse checkout statusElijah Newren via GitGitGadget, Jun 16, 2020
  2. 1/2 [RFC] wt-status: show sparse checkout status as wellElijah Newren via GitGitGadget, Jun 16, 2020
  3. Derrick StoleeJun 17, 2020
  4. Elijah NewrenJun 17, 2020
  5. 2/2 [RFC] git-prompt: include sparsity state as wellElijah Newren via GitGitGadget, Jun 16, 2020
  6. 0/2 Sparse checkout statusElijah Newren via GitGitGadget, Jun 18, 2020
  7. 1/2 wt-status: show sparse checkout status as wellElijah Newren via GitGitGadget, Jun 18, 2020
  8. 2/2 git-prompt: include sparsity state as wellElijah Newren via GitGitGadget, Jun 18, 2020
  9. SZEDER GáborJun 19, 2020
  10. Junio C HamanoJun 19, 2020
  11. Junio C HamanoJun 19, 2020
  12. Junio C HamanoJun 18, 2020
  13. Elijah NewrenJun 18, 2020
  14. Elijah NewrenJun 21, 2020
  15. 0/3 Sparse checkout statusElijah Newren via GitGitGadget, Jun 21, 2020
  16. 1/3 wt-status: show sparse checkout status as wellElijah Newren via GitGitGadget, Jun 21, 2020
  17. 3/3 git-prompt: include sparsity state as wellElijah Newren via GitGitGadget, Jun 21, 2020
  18. Junio C HamanoJun 22, 2020
  19. 2/3 git-prompt: document how in-progress operations affect the promptElijah Newren via GitGitGadget, Jun 21, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.