unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Steinar Bang <sb@dod.no>
Cc: 8756@debbugs.gnu.org
Subject: bug#8756: 23.3; vc-git.el doesn't use --follow argument in vc-git-print-log
Date: Tue, 31 May 2011 01:25:51 -0400	[thread overview]
Message-ID: <yxqy61nh25c.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87sjrxl0r1.fsf@dod.no> (Steinar Bang's message of "Sun, 29 May 2011 22:17:54 +0200")

Steinar Bang <sb@dod.no> writes:

> When pressing `C-x v l' in a git versioned file with a long history,
> that had just been moved, I got just the single commit resulting from
> the move.
>
> If the vc-git-print-log command adds the "--follow" argument, the log
> printed by `C-x v l' is the full history of that file.
>
> Here's the documentation of --follow from the git-log man page:
>        --follow
>            Continue listing the history of a file beyond renames (works only for a single file).

I tried doing that at some point, but the result is not completely
functional, these commands do not work:
 "d" (log-view-diff)
 "f" (log-view-find-revision)  
 "a" (log-view-annotate-revision)

which means that the corresponding vc-git.el functions need updating.
If someone figures out what git commands/sequence of commands are needed
to implement these, then it should not be too hard to implement the
needed changes.





  reply	other threads:[~2011-05-31  5:25 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 [this message]
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
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=yxqy61nh25c.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=8756@debbugs.gnu.org \
    --cc=sb@dod.no \
    /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).