git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: how to track changes of a file

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jun 16, 2008, 16:08 UTC
Message-ID
<48569003.6080406@viscovery.net>
In-Reply-To
<48568B76.5050108@gmail.com>
bill lam schrieb:
Show 11 quoted lines
> Johannes Sixt wrote:
>> $ git rev-list -3 -- glinvc03.ijs
>>
>>
>> $ git show {23335c,31e4f2,b515f0}:glinvc03.ijs
> 
> Thank for you help, but these 2 command did not work, did I missing
> something? I I use git version 1.5.4.3 on linux.
> 
> $ git rev-list -3 -- glinvc03.ijs
> usage: git-rev-list [OPTION] <commit-id>... [ -- paths... ]
Sorry, should have been
$ git rev-list -3 HEAD -- glinvc03.ijs

But this is not intended for daily use anyway. You are better off using git log family of commands. Eg. if you insist on a 1-commit-per-line listing, you'd use

$ git log -3 --pretty=oneline -- glinvc03.ijs
> $ git show {23335c,31e4f2,b515f0}:glinvc03.ijs
> fatal: ambiguous argument '23335c:glinvc03.ijs': unknown revision or
> path not in the working tree.
> Use '--' to separate paths from revisions

My guess is that glinvc03.ijs lives in a subdirectory of your repo. Then you must supply the complete path from the repository root:

$ git show {23335c,31e4f2,b515f0}:some/subdir/glinvc03.ijs
(No, this will not be changed.)
-- Hannes
Previous: bill lam
Message 4 of 4 in “how to track changes of a file”
  1. bill lamJun 16, 2008
  2. Johannes SixtJun 16, 2008
  3. bill lamJun 16, 2008
  4. Johannes SixtJun 16, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.