From: Peter Baumann <siprbaum@stud.informatik.uni-erlangen.de>
To: git@vger.kernel.org
Subject: Re: How do get a specific version of a particular file?
Date: Tue, 27 Feb 2007 13:44:43 +0100 [thread overview]
Message-ID: <slrneu89tr.24s.siprbaum@xp.machine.xx> (raw)
In-Reply-To: E1HM1XL-00071C-N5@candygram.thunk.org
Theodore Ts'o <tytso@mit.edu> schrieb:
>
> So given a particular tree-ish and a pathname, I'd like get the contents
> of that particular file as of a particular revision. i.e., the
> equivalent of:
>
> cvs -r v1.37 -p e2fsck/pass1.c
> or
> bk cat -r 2345 e2fsck/pass1.c
>
> The closest I've been able to come is to use
>
> git archive --format=zip v1.37 e2fsck/pass1.c | gunzip
>
> But that seems kinda silly.
>
> git-checkout will only write the output to the working tree.
> git-cat-file and git-show only work on a object identifier (they are
> low-level plumbing commands).
>
> So if it is a matter of we don't have an easy way to do this (as opposed
> to me being stupid or the git documentation just failing to mention it
> in the right places), what's the best way to add it?
>
> One easy way would be to add --format=raw to git-archive, but that might
> seem counter-intuitive to an average git user; they just want to see the
> output of a file at a particular point in time, which doesn't have much
> to do with archiving.
>
> Should we add a new command like "git-cat"? Should we add a -p option
> to the "git-checkout <treeish> <path>" form of git-checkout?
>
> I'm currently leaning towards the last; it would be pretty simple to
> enhance git-checkout so that a -p option would run "git archive
> --format=zip ...", even though that would be a pretty nasty hack, and it
> wouldn't be much harder to add --format=raw support to git-archive, but
> I still think that's not a intuitive place to find that particular
> functionality.
>
> - Ted
You you could do this with
git show v1.5.0:Makefile
to show you the Makefile in revision v1.5.0.
-Peter
next prev parent reply other threads:[~2007-02-27 12:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 12:34 How do get a specific version of a particular file? Theodore Ts'o
2007-02-27 12:43 ` Christian MICHON
2007-02-27 12:44 ` Peter Baumann [this message]
2007-02-27 12:49 ` Alex Riesen
2007-02-27 12:53 ` Alex Riesen
2007-02-27 12:57 ` Johannes Schindelin
2007-02-27 15:42 ` Theodore Tso
2007-02-27 19:55 ` Johannes Schindelin
2007-02-27 22:39 ` Theodore Tso
2007-02-27 23:25 ` Randal L. Schwartz
2007-02-27 23:35 ` Junio C Hamano
2007-02-28 0:22 ` Linus Torvalds
2007-02-28 0:31 ` Junio C Hamano
2007-02-28 0:39 ` Johannes Schindelin
2007-02-28 0:54 ` Linus Torvalds
2007-02-28 1:11 ` Nicolas Pitre
2007-02-28 1:24 ` Linus Torvalds
2007-02-28 1:48 ` Nicolas Pitre
2007-02-28 2:32 ` Theodore Tso
2007-02-28 2:45 ` Junio C Hamano
2007-02-28 3:03 ` Theodore Tso
2007-02-28 4:33 ` Junio C Hamano
2007-02-28 1:04 ` Nicolas Pitre
2007-02-28 0:01 ` Johannes Schindelin
2007-02-28 0:30 ` Linus Torvalds
2007-02-28 0:33 ` Junio C Hamano
2007-02-28 0:36 ` Johannes Schindelin
2007-02-27 15:43 ` [PATCH] Fix git-show man page formatting in the EXAMPLES section Theodore Tso
2007-02-27 16:38 ` How do get a specific version of a particular file? Linus Torvalds
2007-02-27 17:14 ` Bill Lear
2007-02-27 19:09 ` Theodore Tso
2007-02-27 19:33 ` Linus Torvalds
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=slrneu89tr.24s.siprbaum@xp.machine.xx \
--to=siprbaum@stud.informatik.uni-erlangen.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).