GNU bug report logs -
#8756
23.3; vc-git.el doesn't use --follow argument in vc-git-print-log
Previous Next
Reported by: Steinar Bang <sb <at> dod.no>
Date: Sun, 29 May 2011 20:28:01 UTC
Severity: normal
Tags: fixed
Merged with 19045
Found in versions 23.3, 25.0.50
Fixed in version 26.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
>>>>> Steinar Bang <sb <at> dod.no>:
> Wnen I think of it, it would be simpler to do a "git log --follow
> --name-only" and just regexp out the paths and commits and get an alist
> from commit to path, or something like that...? Actually, you probably
> don't have to create that alist, just doing "git log --follow
> --name-only" just to get the path when you need it, maybe...?
This can be more compact, using
: git log --follow --name-only --pretty=oneline
Here's the compact log for the example file:
#+begin_example
sb <at> somehost:~$ git log --follow --name-only --pretty=oneline apps/share/emacs23/site-lisp/vc-git.el
ae93673cf7a325ac6882b73a4280cfba3fca41e9 Make `vc-git-print-log' on a single file use "git log --follow" instead of "git rev
apps/share/emacs23/site-lisp/vc-git.el
4098e78805561b9af3e29184a8133baaf6d16621 Emacs 23.1 version of vc-git.el.
apps/share/emacs23/site-lisp/vc-git.el
a50a042e5af770928eaa8b636517d66bc2a13ee7 Load the locally modified vc-git.el only for emacs23 (fails on emacs22).
apps/share/emacs23/site-lisp/vc-git.el
8d304db76993a0da0894b3d30794a2c5ec4927fe Use the --follow flag on the "git log" command, to get full history across file mov
apps/share/emacs/site-lisp/vc-git.el
a92a3d062dac1b0ec5eece4ed6f9570e59f1a69b Adding the vc-git.el from emacs 23.3.
apps/share/emacs/site-lisp/vc-git.el
#+end_example
Should be fairly easy to get a path for a commit, from this...?
This bug report was last modified 5 years and 252 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.