Le mercredi 4 juin 2014 16:28:27 UTC+2, Dale Worley a écrit : > > Yeah, but what one *feels* is the definition of the word is not > relevant. > It somehow is IMO, as I got that feeling from my day-to-day use of git and from reading its manual, so it might be the symptoma of some incoherences across the tool's usage and/or definitions. Le mercredi 4 juin 2014 16:28:27 UTC+2, Dale Worley a écrit :
> The online book is particularly treacherous: > http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository > <http://www.google.com/url?q=http%3A%2F%2Fgit-scm.com%2Fbook%2Fen%2FGit-Basics-Recording-Changes-to-the-Repository&sa=D&sntz=1&usg=AFQjCNFeXBzZKfP7X6tUZSl8GVa-BeV9Qg> > > > Remember that each file in your working directory can be in one of > two states: tracked or untracked. Tracked files are files that > were in the last snapshot; they can be unmodified, modified, or > staged. Untracked files are everything else — any files in your > working directory that were not in your last snapshot and are not > in your staging area. > > If you read carefully, you'll note that it is self-contradictory: His > definition of tracked excludes staged-but-not-in-the-head-commit files > but his definition of untracked also excludes those files. > It is a bit self-contradictory, but only in the listing of what such files can be. Apart from that, the definition *"Tracked files are files that were in the last snapshot [...]. Untracked files are everything else"* is pretty clear, and describes exactly my understanding of such files. So, to answer André's original question, I think might indeed be either a bug or a missing feature. I think I'm gonna mail g...@vger.kernel.org (the "official" mailing list <http://git-scm.com/community>) to see what they think about it. Would it be wrong to reply to this conversation with a summary of it, CC'ed to g...@vger.kernel.org? I'm not quite confident with using public mailing lists just yet. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
