From: Theodore Tso <tytso@MIT.EDU>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Florian Weimer <fw@deneb.enyo.de>, git@vger.kernel.org
Subject: Re: What I miss from Cogito...
Date: Sun, 23 Mar 2008 22:14:11 -0400 [thread overview]
Message-ID: <20080324021411.GE24943@mit.edu> (raw)
In-Reply-To: <20080324014030.GA24695@atjola.homenet>
On Mon, Mar 24, 2008 at 02:40:30AM +0100, Björn Steinbrink wrote:
> > If we were going to separate the two commands out, I'd use the name
> > "git revert-file", because that's what people who are coming from bk
> > or hg are used to (where "revert" means to undo the local edits done
> > to a particular file, as opposed to the git meaning of undoing a
> > particular commit).
>
> Nah, that would create confusion within git, because it does something
> totally different from git revert. And checkout can also checkout a
> whole tree, not just a file. So you would either need revert-tree as
> well... Or add more confusion, because revert-file "reverting" a tree is
> not quite intuitive.
That's why I said "git revert-file" as being different from "git
revert". If you want to revert the entire tree in the sense of
"undoing local edits", most people today use "git reset --hard".
> Maybe it's just a misunderstanding on my side, but to me "checkout"
> means as much as "get me something out of the repo".
If that's true, why is the one-line summary in the git-checkout man
page and in the git top-level man page read as follows?
git-checkout - Checkout and switch to a branch
At the very least, will you admit that the summary in the man page is
perhaps just a wee bit misleading?
- Ted
next prev parent reply other threads:[~2008-03-24 2:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 17:15 What I miss from Cogito H. Peter Anvin
2008-03-23 17:38 ` Theodore Tso
2008-03-23 17:46 ` H. Peter Anvin
2008-03-27 2:36 ` Petr Baudis
2008-03-23 18:21 ` Luciano Rocha
2008-03-23 19:00 ` Mike Hommey
2008-03-23 19:07 ` Bruce Stephens
2008-03-23 19:07 ` Mike Hommey
2008-03-23 19:14 ` Florian Weimer
2008-03-24 0:16 ` Theodore Tso
2008-03-24 1:40 ` Björn Steinbrink
2008-03-24 2:14 ` Theodore Tso [this message]
2008-03-24 2:53 ` Junio C Hamano
2008-03-24 2:57 ` Björn Steinbrink
2008-03-24 3:06 ` [PATCH] Documentation/git-checkout: Update summary to reflect current abilities Julian Phillips
2008-03-24 16:49 ` Junio C Hamano
2008-03-24 3:06 ` Julian Phillips
2008-03-23 18:31 ` What I miss from Cogito Johannes Schindelin
2008-03-23 18:34 ` Junio C Hamano
2008-03-23 18:58 ` H. Peter Anvin
2008-03-23 18:59 ` Junio C Hamano
2008-03-23 19:16 ` Daniel Barkalow
2008-03-23 19:19 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080324021411.GE24943@mit.edu \
--to=tytso@mit.edu \
--cc=B.Steinbrink@gmx.de \
--cc=fw@deneb.enyo.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).