A truly linear file history

[Angel Ezquerra]

El 22/10/2013 20:04, "Bob Hood" <bhood2 at comcast.net> escribió:
>
> On 10/22/2013 10:44 AM, Simon King wrote:
> > On Tue, Oct 22, 2013 at 3:37 PM, Bob Hood <bhood2 at comcast.net> wrote:
> >> This is a log mining question.
> >>
> >> I'm amusing myself by writing a utility that does a Subversion-like
"blame"
> >> mechanism for a Mercurial repository.  I have it working, but I'm
running
> >> into a problem with the "hg log" command.  I cannot seem to find the
right
> >> combination of command-line options to produce a fully linear file
history,
> >> running from the point of introduction (initial check-in) up to the
> >> last/latest change.  This is required in order to faithfully
reconstruct the
> >> current state of the file.
> > Just to check: you do know about "hg blame", don't you?
>
>
> Actually, no, I didn't know about that.  I knew about TortoiseHG's
"Annotate
> Files", but I didn't realize there was an actual "blame" function (which
it
> would appear, "Annotate Files" uses).
>
> That greatly simplifies my project.  Thanks.  ;)

Actually there is also an "hg annotate" command. "hg blame" is just an
alias for "hg annotate". That is why the TortoiseHg command is called
"annotate".

Cheers,

Angel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20131022/5fcff21a/attachment-0002.html>