{"thread":{"id":"12843","subject":"BUG:git-log --follow <path> should never trim output WRT equivalent git-log <path>","startedAt":"2008-03-24T16:19:01Z","lastAt":"2008-03-25T01:45:04Z","messageCount":2,"participants":["Santiago Gala","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"72908","messageId":"loom.20080324T161602-184@post.gmane.org","threadId":"12843","inReplyTo":null,"subject":"BUG:git-log --follow <path> should never trim output WRT equivalent git-log <path>","fromName":"Santiago Gala","fromEmail":"sgala@apache.org","sentAt":"2008-03-24T16:19:01Z","receivedAt":"2008-03-24T16:19:01Z","isPatch":false,"sender":{"key":"sgala@apache.org","avatar":"https://gravatar.com/avatar/3ce198370fff616e4d4b6d85d86f657c2d18762b036bf8cdf7330150f51c7558?d=mp&s=160"},"body":"I tried this on today's git.git repository, as a suggestion for following moves:\n\n$ git log  -M -C -C --color --stat --follow -- gitk-git/po/de.po | wc -l\n0\nsgala@marlow ~/newcode/git/git (master)$ git log  -M -C -C --color --stat --\ngitk-git/po/de.po | wc -l\n31\n$ git --version\ngit version 1.5.4.4\n\nI find very strange that --follow makes git log to stop outputting the first\nentries.\n\nRegards\nSantiago\n"},{"id":"72996","messageId":"20080325014504.GA15864@coredump.intra.peff.net","threadId":"12843","inReplyTo":"loom.20080324T161602-184@post.gmane.org","subject":"Re: BUG:git-log --follow <path> should never trim output WRT equivalent git-log <path>","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2008-03-25T01:45:04Z","receivedAt":"2008-03-25T01:45:04Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Mar 24, 2008 at 04:19:01PM +0000, Santiago Gala wrote:\n\n> $ git log  -M -C -C --color --stat --follow -- gitk-git/po/de.po | wc -l\n> 0\n> sgala@marlow ~/newcode/git/git (master)$ git log  -M -C -C --color --stat --\n> gitk-git/po/de.po | wc -l\n> 31\n> $ git --version\n> git version 1.5.4.4\n> \n> I find very strange that --follow makes git log to stop outputting the first\n> entries.\n\nI think the tricky thing here is that every one of those commits is a\nmerge, which doesn't actually \"introduce\" any content, and that probably\nconfuses the \"--follow\" code.\n\nThe thing is that getting the history of gitk-git specifically is a bit\ntricky. All of the commits actually happen to, e.g., the file 'gitk' in\nthe main gitk repository, and then Junio merges it into git using a\nspecial \"subtree\" merge as 'gitk-git/gitk'. So looking at a path in\n'gitk-git' will always just turn up merge commits; the actual commits\ntook place on a different path.\n\nBut I haven't looked too closely at what's going on, so I may be way off\nbase. My two cents.\n\n-Peff\n"}]}