Santi Béjar <santi@xxxxxxxxxxx> writes: > 2009/1/30 Frank Li <lznuaa@xxxxxxxxx>: > > mkdir tt3 > > cd tt3 > > git init-db > > "git init" > > > touch a.c > > git add a.c > > git commit -a -m "test1" > > > > git mv a.c b.c > > git commit -a -m "rename" > > > > modify b.c > > git commit -a -m "test2" > > > > git log -C -M -- b.c > [...] > > I can't get history before rename. > > You asked to restrict the search to the b.c path. > > You want: > > git log --follow -- b.c > > Man git-log: > --follow > Continue listing the history of a file beyond renames. Or use $ git log -C -- b.c a.c (you don't need '-M' option, as '-C' is superset of it). Note that '--follow' works for simple histories, but (as it is quite new invention) doesn't work yet for all cases, like for example subtree merge or equivalent. -- Jakub Narebski Poland ShadeHawk on #git -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
