Fri 23 Jun 2006 12:09:43 PM UTC, original submission:
When I run mtn log with a filename argument, I get back a bunch of what seem to be entirely spurious results - revisions that don't seem to have anything to do with the file in question.
For example, with n.v.m:
$ mtn log INSTALL
-----------------------------------------------------------------
Revision: 7e91b0be841df09bc6b660c5daa7149bf7cd7f2c
Ancestor: bee07943ec6470fbbdd475787ad3f28cbaa94155
Author: -unavailable-
Date: 2006-06-20T09:50:21
Branch: net.venge.monotone
Modified files:
ChangeLog INSTALL
ChangeLog:
2006-06-20 Nathaniel Smith <njs@pobox.com>
* INSTALL: Update a little bit, in particular, give a newer boost
download link in response to complaint on mailing list, and put
1.9 version number on automake command line.
-----------------------------------------------------------------
Revision: b211c8fd09d534667af859051654b20ae599f57b
Ancestor: bc31e4146981d7a234e337316e66f9d55340ce0b
Author: -unavailable-
Date: 2006-06-20T08:12:25
Branch: net.venge.monotone
Deleted entries:
tests/atconfig.in tests/atlocal.in
Modified files:
ChangeLog Makefile.am
ChangeLog:
2006-06-20 Nathaniel Smith <njs@pobox.com>
* Makefile.am (EXTRA_DIST): The auto* gods demand sacrifice;
remove an extra / to balance previous change.
(NB: apparently a trailing / on a directory in EXTRA_DIST does
bizarre things.)
Also, remove empty files tests/atconfig.in, tests/atlocal.in.
-----------------------------------------------------------------
...
In this case, the first revision log prints is actually an edit of INSTALL, but the second isn't. Am I completely misunderstanding how `mtn log` is supposed to work with a path argument?
It is also dog-freakin-slow when you pass an argument. I'm perfectly willing to tolerate slow-but-works, though. :)
|