Aha, that clears up a few things. Thanks for the great explanation!
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to
git-users
On Thu, 27 Jan 2011 02:20:20 -0800 (PST)
Thomas Ferris Nicolaisen wrote:
> Brilliant, that was simpler than I could imagine :)
>
> Do you know if the dashes are even necessary? Here it worked without
> them.
Not necessary as long as Git can figure out you mean a pathname, not
a branch name. In
Brilliant, that was simpler than I could imagine :)
Do you know if the dashes are even necessary? Here it worked without them.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-users@googlegroups.c
On Thu, 27 Jan 2011 01:48:02 -0800 (PST)
Thomas Ferris Nicolaisen wrote:
> Say I have this:
>
> # On branch master
> # Changes to be committed:
> # (use "git reset HEAD ..." to unstage)
> #
> # modified: foo
> #
> # Changed but not updated:
> # (use "git add ..." to update what will be com
Say I have this:
# On branch master
# Changes to be committed:
# (use "git reset HEAD ..." to unstage)
#
# modified: foo
#
# Changed but not updated:
# (use "git add ..." to update what will be committed)
# (use "git checkout -- ..." to discard changes in working
directory)
#
# modified:
