From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Eli Barzilay <eli@barzilay.org>, git <git@vger.kernel.org>
Subject: Re: Feature request: relative paths
Date: Thu, 6 May 2010 10:46:07 +0200 [thread overview]
Message-ID: <20100506084607.GA9921@atjola.homenet> (raw)
In-Reply-To: <20100506083113.GA25993@progeny.tock>
On 2010.05.06 03:31:13 -0500, Jonathan Nieder wrote:
> Eli Barzilay wrote:
>
> > An svn feature that I used a lot is `svn cat some-file' -- and with
> > git I can get close to that with `git show :some-file'
>
> git show -- some-file
That's the same as "git show HEAD -- some-file" though, which shows a
commit with path-limited diff output. While ":some-file" (most likely)
identifies a blob, so "git show :some-file" shows the contents stored in
that blob.
Björn
next prev parent reply other threads:[~2010-05-06 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 6:01 Feature request: relative paths Eli Barzilay
2010-05-06 8:31 ` Jonathan Nieder
2010-05-06 8:46 ` Björn Steinbrink [this message]
2010-05-06 9:01 ` Jonathan Nieder
2010-05-06 9:09 ` Jeff King
2010-05-06 9:04 ` Jeff King
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=20100506084607.GA9921@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=eli@barzilay.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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).