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

Re: [PATCH 0/6] "git commit --dry-run" updates

From
Thomas Rast <trast@student.ethz.ch>
Date
Aug 17, 2009, 19:16 UTC
Message-ID
<200908172116.26737.trast@student.ethz.ch>
In-Reply-To
<7vljlixwkz.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
Show 11 quoted lines
> Thomas Rast <trast@student.ethz.ch> writes:
> 
> > If it's not too much work, it would be nice to somehow detect if -u
> > can have any influence at all.  For example,
> >
> >   $ git status bar
> >   # Not currently on any branch.
> >   nothing to commit (use -u to show untracked files)
> >
> > is a bit misleading if 'bar' is tracked because adding a -u won't make
> > any difference.
[...]
> It is not about "we know that there are untracked files but you told me
> not to show it, so I am not telling".  We simply do not know at the point
> we give that message.  In other words, conditional removal of that message
> is fundamentally incompatible with the use of -uno.

Ok. I hoped there would be an easy way to know that all pathspecs exactly matched a tracked file, and thus no untracked files can possibly change the listing.

But you convinced me that it doesn't fit into the current scheme, and it doesn't really matter...

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Junio C Hamano
Message 10 of 10 in “"git commit --dry-run" updates”
  1. 0/6 "git commit --dry-run" updatesJunio C Hamano, Aug 15, 2009
  2. 1/6 Documentation/git-commit.txt: describe --dry-runJunio C Hamano, Aug 15, 2009
  3. 2/6 git commit --dry-run -v: show diff in color when askedJunio C Hamano, Aug 15, 2009
  4. 3/6 git stat: the beginningJunio C Hamano, Aug 15, 2009
  5. 4/6 git stat: pathspec limits, unlike traditional "git status"Junio C Hamano, Aug 15, 2009
  6. 5/6 git stat -s: short status outputJunio C Hamano, Aug 15, 2009
  7. 6/6 git status: not "commit --dry-run" anymoreJunio C Hamano, Aug 15, 2009
  8. Thomas RastAug 17, 2009
  9. Junio C HamanoAug 17, 2009
  10. Thomas RastAug 17, 2009

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.