Re: [PATCH v2] git-checkout.txt: Document "git checkout <pathspec>" better

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 17/06/15 13:54, Matthieu Moy wrote:
"Andres G. Aragoneses" <knocte@xxxxxxxxx> writes:

On 17/06/15 12:54, Matthieu Moy wrote:
Duy Nguyen <pclouds@xxxxxxxxx> writes:

On Wed, Jun 17, 2015 at 2:54 PM, Torsten Bögershausen <tboegi@xxxxxx> wrote:
-git-checkout - Checkout a branch or paths to the working tree
+git-checkout - Switch branches or restore changes

I didn't follow closely the previous discussion.

(Neither did I)

Forgive me if this is already discussed, but I would keep the "in the
working tree". "Restore changes" alone seems vague.

"Restore previous version" would be better than "Restore changes" to me.

"previous version" sounds ambiguous.

Yes, but "git checkout" can do many things. It can restore an old
commited state, restore from the index, ... so we need to either be
vague, or use a long enumeration.

How about "discard local changes"?

To me this describes "git checkout HEAD", but neither "git checkout --
file" nor "git checkout HEAD^^^".


I didn't mean to use just "discard local changes". I was proposing that as a replacement to the "restore changes" substring.

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]