Re: [Monotone-devel] mtn log's file restrictions

[Nathaniel Smith]

On Mon, Aug 21, 2006 at 10:18:21AM +0200, Lapo Luchini wrote:
> % mtn log it.po --no-merges --brief
> 3783598ecae9ff2022e07b1ffd8e2091666bf0ef address@hidden
> 2006-08-07T09:20:15 net.venge.monotone
> 6a5baf664a11c7687178ca8fd527c47956976925 address@hidden
> 2006-08-07T08:55:22 net.venge.monotone
> b9e35621f382f0cd2cd2d6d7b3b26b25e356ce0f address@hidden
> 2006-07-27T20:04:57 net.venge.monotone
> 4c31eda84d5cae93bbef6e7cf3b69a38ad6fc9be address@hidden
> 2006-07-25T07:39:05 net.venge.monotone
> [...]
> ecba1086828e28ad4d723c7472a19f9265cfd74a address@hidden
> 2003-11-16T23:54:16 net.venge.monotone
> 7a348bde71e41b194916cc78ee83cca55698da55 address@hidden
> 2003-10-31T19:57:24 net.venge.monotone
> aa5c2e90efa2ed1c1d1475adb7aaa022f730e5bb address@hidden
> 2003-09-27T06:42:59 net.venge.monotone
> 5d3f6f09fac7f7fb4a3df75a7a2d16dfe78f5b8c address@hidden
> 2003-09-06T21:10:10 net.venge.monotone
> 
> ...but indeed not! Just to be sure I tried starting from one of those
> revisions:
> 
> % mtn log it.po --no-merges -r 01f1dceee7a20e355c8c46ac955dfdf424667f1f
> mtn: warning: restriction includes unknown path 'po/it.po'
> mtn: misuse: 1 unknown paths
> 
> ...with the expected answer. Why was it in the first output at all, then?

What version of monotone?  I suspect it's related to this item in the
0.29 release notes:

        - 'mtn log <FILES>' formerly listed irrelevant revisions (in
          particular, any revision which contained a delete of any files
          or directories, was always included).  This has been fixed.

Try using 0.29/current mainline.

Possible alternative way to get what you want:
  mtn automate select a:address@hidden | mtn automate toposort address@hidden | 
head -n 1

-- Nathaniel

-- 
Eternity is very long, especially towards the end.
  -- Woody Allen