[PATCH] hgweb: follow renames and copies in file log (issue1576)

[Martin Geisler]

Matt Mackall <mpm at selenic.com> writes:

> Similarly, it'd be highly confusing if hg log's default output were
> tied to the current working directory contents, especially if the
> working directory were in the 'past', thus causing future changes not
> to be shown.

You may think so, but it's not as clear cut as that. I know you don't
"speak Git", but if you look at Git, then you'll see that they do infact
use the equivalent of 'hg log -f' by default.

I have tried to introduce people to Mercurial and they were *confused*
about the fact that 'hg log' still showed later revisions when they
updated back. They did not know about Git.

It would actually be interesting if 'hg log' was 'hg log -f' by default
and if it then outputted a message to indicate that there is more
changesets "above" those shown:

  $ hg update 5065e120636d
  0 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ hg log -f -l 2
  (2 changesets not shows)

  changeset:   13904:5065e120636d
  branch:      stable
  parent:      13901:d3890ead75be
  user:        Martin Geisler <mg at aragost.com>
  date:        Thu Apr 07 11:17:55 2011 +0200
  summary:     hgrc.5: drop 'hgext.' prefix when talking about extensions

  changeset:   13901:d3890ead75be
  branch:      stable
  parent:      13900:a3403d5b0af3
  parent:      13882:0a0988bd4818
  user:        Matt Mackall <mpm at selenic.com>
  date:        Wed Apr 06 15:13:49 2011 -0500
  summary:     merge with crew

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://mercurial.aragost.com/kick-start/