Re: [ctwm] ctwm-3.8b? ctwm-3.9?

2009-08-21 Thread Aaron Sloman
Kai wrote:

 On 08/20/2009 03:15 PM, Aaron Sloman wrote:
  Unfortunately monontone has a terrible bug: unlike wget, it loses
  all information about when the files were created, so I don't know
  how old this system is.

 Given that Monotone is a version control system, I'd expect mnt log or
 a similar command to show you the list of changes.  That would give you
 the date you're looking for.

And so it does!

'mnt log' tells me that files changed since 2007 are:

Date: 2009-06-13T06:42:13
 |   menus.c
Date: 2009-06-13T06:10:55
 |   workmgr.c
Date: 2008-10-28T14:27:17
 |   menus.c
Date: 2007-12-29T16:08:28
 |   workmgr.c

(There's much more in the output.)

I'll have to look more closely if I ever want to understand all the
detail in the log output.

Many thanks.

Aaron
http://www.cs.bham.ac.uk/~axs



Re: [ctwm] ctwm-3.8b? ctwm-3.9?

2009-08-21 Thread Matthew D. Fuller
On Fri, Aug 21, 2009 at 12:47:05AM +0100 I heard the voice of
Aaron Sloman, and lo! it spake thus:
 
 It turns out that monotone also loses the information.

This isn't really accurate.  It's all there (as it would have to be,
to fulfill its purpose), it just doesn't set mtime on the files.  And
it shouldn't a VCS doing that is bogus for various reasons (the most
obvious being that it screws up make).


  ...if you know what 'vcs' is, which I don't -- Sorry!

http://en.wikipedia.org/wiki/Version_control_system

It sounds like you're thinking of mtn as if it were something like a
FTP client (or FTP server, depending).  It's not really for
downloading or dealing with files; as a VCS, its meant to deal with
_history_.  You didn't download the files, you downloaded the whole[0]
history of the ctwm project.  It's a side effect of that, that you can
checkout the tree as it existed at any arbitrary point of its history
(specifically, you checked it out as of the latest change that's been
checked in, which at the moment is an adjustment to
OpaqueResizeThreshold I made in June).  There isn't any 3.9-devel
release or snapshot to download, that's just what every revision since
the 3.8a release was made calls itself, since it has to call itself
SOMEthing.

Trying to talk about all the ways of examining history would be way
out of place here, but the simplest is just 'mtn log', which gives you
a log of the changes to the project.  'mtn log $FILE' lets you limit
to a single file.  Various args to 'mtn diff' let you look at the
specific changes made in a [set of] revision[s], maybe limited to a
single file.  Et cetera.  Hitting the mtn docs would be the place for
details.


 I had hoped that the standard specification would simply determine a
 list of operations required, which could be installed without read
 any code that will invoke them. But perhaps EWMH is not clear enough
 for that. I haven't looked at it.

Well, it may.  I've only glanced at it.  But it's a huge list; it's
likely that only one or two of the properties are important here.



[0] Not really; any revision history prior to using mtn (or maybe CVS
before that; I'm not sure how much Richard imported) isn't in the
repo, though it does have very coarse-grained release imports back
to ctwm 1.1.  But close enough.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.