From: Bruce Stephens <bruce.stephens@isode.com>
To: Mike Hommey <mh@glandium.org>
Cc: Luciano Rocha <luciano@eurotux.com>, Theodore Tso <tytso@MIT.EDU>,
"H. Peter Anvin" <hpa@zytor.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What I miss from Cogito...
Date: Sun, 23 Mar 2008 19:07:35 +0000 [thread overview]
Message-ID: <80eja1uumg.fsf@tiny.isode.net> (raw)
In-Reply-To: <20080323190017.GB16893@glandium.org> (Mike Hommey's message of "Sun\, 23 Mar 2008 20\:00\:17 +0100")
Mike Hommey <mh@glandium.org> writes:
> On Sun, Mar 23, 2008 at 06:21:02PM +0000, Luciano Rocha wrote:
[...]
>> I use git checkout path ...
>>
>> Isn't that the same thing?
>
> Yes, it does the same. Note there is unfortunately no shorthand for
> git show $arbitrary_commit:$path > $path
Isn't that what
git checkout $arbitrary_commit -- $path
does?
next prev parent reply other threads:[~2008-03-23 19:08 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 [this message]
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
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=80eja1uumg.fsf@tiny.isode.net \
--to=bruce.stephens@isode.com \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=luciano@eurotux.com \
--cc=mh@glandium.org \
--cc=tytso@MIT.EDU \
/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).