From: Uwe Brauer <oub@mat.ucm.es>
To: Glenn Morris <rgm@gnu.org>
Cc: Uwe Brauer <oub@mat.ucm.es>, 22470@debbugs.gnu.org
Subject: bug#22470: 25.1.50; vc-annotate (HG) does not display changes within one day (colors)
Date: Tue, 26 Jan 2016 19:18:47 +0000 [thread overview]
Message-ID: <87si1k5eug.fsf@mat.ucm.es> (raw)
In-Reply-To: <87wpqwick6.fsf@mat.ucm.es>
>>> "GM" == Glenn Morris <rgm@gnu.org> writes:
> Uwe Brauer wrote:
>> For master vc-annotate displays the lines all in the same color while
>> emacs-25-branch distinguish them.
> FWIW, I see no difference between current master and emacs-25.
> It also seems self-evident to me that if you've set the date to only
> display at the level of days, you'll only get colouring at the same
> level.
Well I hoped one could generate coloring which reflects changes within
the day, but display the time format deleting the hours and minutes but
it seems not to be possible.
> The current vc-annotate behavior for hg seems consistent with eg git.
Well but I still think it were better to display changes which occur
within a day.
> Finally, at a very quick glance that ahg thing seems to colorize
> based on revision number, not on age, which is a different scheme.
By revision number do you mean the changeset or the internal local
revision number which hg assigns to its commits but git does not? If it
is the former, maybe that would be a more appropriate model for
vc-annotate?
> So personally I see no bug here.
I did not use the word bug, I was asked to send a bug report in order to
find out whether there is a bug.
next prev parent reply other threads:[~2016-01-26 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 15:29 bug#22470: 25.1.50; vc-annotate (HG) does not display changes within one day (colors) Uwe Brauer
2016-01-26 18:50 ` Glenn Morris
2016-01-26 19:18 ` Uwe Brauer [this message]
2016-01-27 0:35 ` Dmitry Gutov
2016-01-27 16:42 ` Glenn Morris
2016-01-27 0:03 ` Dmitry Gutov
2016-01-27 17:43 ` Glenn Morris
2016-01-27 0:40 ` Dmitry Gutov
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=87si1k5eug.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=22470@debbugs.gnu.org \
--cc=rgm@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).