[9fans] contrib tracker

[9fans] contrib tracker

[John Floren]

I've written a little script to go through contrib and generate a
markdown page showing what the last update time for the files it
finds, all the way back to the start of the year. At some point I may
extend it to go into previous years as well, but except for during
early January of each year the current system should be sufficient to
keep an eye on what's new/updated on contrib.

I've set up a cron job to update the page daily:
http://csplan9.rit.edu/users/john/contrib.html

John
--
"Object-oriented design is the roman numerals of computing" -- Rob Pike

Re: [9fans] contrib tracker

[erik quanstrom]

> I've written a little script to go through contrib and generate a
> markdown page showing what the last update time for the files it
> finds, all the way back to the start of the year. At some point I may
> extend it to go into previous years as well, but except for during
> early January of each year the current system should be sufficient to
> keep an eye on what's new/updated on contrib.
>
> I've set up a cron job to update the page daily:
> http://csplan9.rit.edu/users/john/contrib.html

great.  this is useful.

unfortunately, ....

since your script keys off the modification time,
which can be change with a wstat, your program
misses (at least) things moved with replica that were not
moved the same day they were modified.  for example:

	; f=/contrib/quanstro/root/sys/src/cmd/upas/fs/mbox.c
	; d = (2009/0807 2009/0806)
	; diff /n/sourcesdump/^$d^$f >/dev/null || echo diffs
	diffs

yet your markdown page does not show the difference.
history(1) tends to give output misleading in the same way.

- erik