From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@gnu.org>
Cc: 8756@debbugs.gnu.org, sb@dod.no
Subject: bug#8756: 23.3; vc-git.el doesn't use --follow argument in vc-git-print-log
Date: Sun, 12 Jan 2014 05:57:21 +0200 [thread overview]
Message-ID: <83vbxp97j2.fsf@gnu.org> (raw)
In-Reply-To: <yxq61pq6kfu.fsf@fencepost.gnu.org>
> From: Dan Nicolaescu <dann@gnu.org>
> Date: Sat, 11 Jan 2014 20:46:45 -0500
> Cc: 8756@debbugs.gnu.org
>
> IMO the ideal solution is to get git to put the sha1/path info in the
> log output, then vc can read it from there and do whatever is needed.
> Is it possible to do that using the "format" argument to git log?
Yes, use %H or %h.
> Another thing that could be improved in the log output (C-x v L) is to
> put the date before the name.
>
> >From a random place in emacs history:
>
> * 2822e57..: Paul Eggert 2013-01-14 Avoid needless casts with XSAVE_POINTER.
> * 5dece9d..: Leo Liu 2013-01-14 Sync window-point and point in calendar-redraw
> * 9b1cf40..: Glenn Morris 2013-01-14 Auto-commit of loaddefs files.
> * df32ded..: Dmitry Antipov 2013-01-14 * lisp.h (toplevel): Fix typo in comment.
>
> The date has a fixed length, names do not, the display would look much better like this:
>
> * 2822e57..: 2013-01-14 Paul Eggert Avoid needless casts with XSAVE_POINTER.
> * 5dece9d..: 2013-01-14 Leo Liu Sync window-point and point in calendar-redraw
> * 9b1cf40..: 2013-01-14 Glenn Morris Auto-commit of loaddefs files.
> * df32ded..: 2013-01-14 Dmitry Antipov * lisp.h (toplevel): Fix typo in comment.
The 'format' option supports alignment directive, so the format of the
output could be even prettier.
Here's what I use for a pretty log output:
git log --pretty='format:%h %<(18,mtrunc)%an %cd %s' --date=short
next prev parent reply other threads:[~2014-01-12 3: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
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 [this message]
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=83vbxp97j2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=8756@debbugs.gnu.org \
--cc=dann@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).