From: Steinar Bang <sb@dod.no>
To: Dan Nicolaescu <dann@gnu.org>
Cc: 8756@debbugs.gnu.org
Subject: bug#8756: 23.3; vc-git.el doesn't use --follow argument in vc-git-print-log
Date: Thu, 01 Dec 2011 22:57:24 +0100 [thread overview]
Message-ID: <87sjl4neez.fsf@dod.no> (raw)
In-Reply-To: <87wragnf08.fsf@dod.no> (Steinar Bang's message of "Thu, 01 Dec 2011 22:44:38 +0100")
>>>>> Steinar Bang <sb@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@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...?
next prev parent reply other threads:[~2011-12-01 21:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 20:17 bug#8756: 23.3; vc-git.el doesn't use --follow argument in vc-git-print-log Steinar Bang
2011-05-31 5:25 ` Dan Nicolaescu
2011-11-28 20:21 ` Steinar Bang
2011-11-28 21:08 ` Dan Nicolaescu
2011-11-29 17:29 ` Steinar Bang
2011-12-01 18:15 ` Dan Nicolaescu
2011-12-01 21:44 ` Steinar Bang
2011-12-01 21:57 ` Steinar Bang [this message]
2014-01-09 19:21 ` Glenn Morris
2014-01-11 1:40 ` Dan Nicolaescu
2014-01-11 14:15 ` Steinar Bang
2014-01-11 23:32 ` Steinar Bang
2014-01-12 1:46 ` Dan Nicolaescu
2014-01-12 3:57 ` Eli Zaretskii
2014-01-12 10:15 ` Steinar Bang
2014-01-12 10:45 ` Steinar Bang
2014-07-30 20:35 ` bug#8756: " Dmitry Dzhus
2019-11-03 14:32 ` Lars Ingebrigtsen
2019-11-03 18:48 ` Dmitry Gutov
2019-11-08 20:44 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sjl4neez.fsf@dod.no \
--to=sb@dod.no \
--cc=8756@debbugs.gnu.org \
--cc=dann@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).