From: Florian Weimer <fw@deneb.enyo.de>
To: git@vger.kernel.org
Subject: Re: What I miss from Cogito...
Date: Sun, 23 Mar 2008 20:14:47 +0100 [thread overview]
Message-ID: <87r6e1b6c8.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20080323182102.GA22551@bit.office.eurotux.com> (Luciano Rocha's message of "Sun, 23 Mar 2008 18:21:02 +0000")
* Luciano Rocha:
>> git show HEAD:$prefix$i > $i
> I use git checkout path ...
>
> Isn't that the same thing?
No, it restores the file version in the index. "git checkout HEAD --
$path" should be the same.
Personally, I'm not all that happy with the multiple different meanings
of "git reset" and "git checkout", either. Depending on the parameters,
the two comments manipulate both the contents of the working copy, or
the location at which the working copy is hooked in the history. If we
need to have two separate commands for this, it would make more sense to
draw distinction between the two aspects, and not the mess we have now.
OTOH, it's probably too late for that.
next prev parent reply other threads:[~2008-03-23 19: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 [this message]
2008-03-24 0:16 ` Theodore Tso
2008-03-24 1:40 ` Björn Steinbrink
2008-03-24 2:14 ` Theodore Tso
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=87r6e1b6c8.fsf@mid.deneb.enyo.de \
--to=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).