----- Original Message ----- 
  From: Pierre-François CLEMENT 
  To: git-users@googlegroups.com 
  Sent: Thursday, June 05, 2014 11:21 AM
  Subject: Re: [git-users] Re: git reset with staged changes


  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 

        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) 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.

There's been a recent thread about almost the same subject on the git mailing 
list.
http://thread.gmane.org/gmane.comp.version-control.git/250500

It may be worth piggy-backing on that.

Don't forget the git list requires pure plain text emails.

(This thread is https://groups.google.com/forum/#!topic/git-users/27_FxIV_100 
if you need that reference;-)

Philip
--

-- 
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.

Reply via email to