(2013/09/14 13:37), Reuben Morais wrote:
On Sep 11, 2013, at 12:04 PM, Scott Johnson <sjohn...@mozilla.com> wrote:
I understand the merit of leaving the code as is since hg blame won't work
nicely with such file-wide format change as in step-1.
(Or maybe we can teach hg blame to ignore such change, etc. but maybe too
much work: the idea would be to mark formatting change with a particular
string [maybe tag name] and let hg blame to ignore such tag to look for a
previous patch that touched each line. Hmm. Maybe too much work indeed)
It would be really nice if we could somehow teach hg blame to ignore
style changes, but I think that's probably a very involved task. ;)
Mercurial is very extensible, the easy way to do this is to simply flag style
changing commits with metadata and then use that during blame.
-- reuben
Thank you for an interesting idea. Yes, if we mark style change as such, then
hg blame can do something clever about it.
(At the same time, I don't want to put too much work on whoever is doing the hg
infrastructure work.
It is an amazing piece of engineering work. I Thank whoever is/are doing the
work
for providing the database to the public.
Being a programmer of a yester-year generation, I still sometimes find it
awkward to
refer to the hg database [my motto is that the source file ought to carry all
the relevant information],
but hg database and especially its web frontend (including mxr) has proved very
useful. Thx.)
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
