Hi,
If you prepare a README (possibly as HTML for easier reading), nicely
formatted, with the author's name and email address as well as a license
statement, I'll include that in some contrib/ directory in the next release -
if you want that.
Will try.
I already have new version. Not sure is it useful, because it is
using 'svnadmin dump' (the same output format as 'svn proplist'):
$ svnadmin dump --incremental | tr -dc '[:print:]\n' | awk ... >
'incremental-rev2'
$ join 'props-rev1' 'incremental-rev2' > 'props-rev2'
Old version created each report in 20 minutes. To compare 2 revisions
you need to 'diff/join' 2 reports (or 40 minutes).
This version, for empty revisions, works very fast (it is incremental).
For the largest commit (max number of files, initial commit, ,etc) it
takes 2-4 min. Or total 40 minutes for 90 revisions.
Plus 'diff/join' 2 reports could be optimized. Instead 'diff/join'
props-rev10 and props-rev15 (both full reports). It could be:
'(join from incremental-rev11 to incremental-rev15)' and then
'diff/join' with props-rev14
Hope explanation is good.
A link has no properties, apart from svn:special. It has no mode, no owner and
group; if you try a chown on a link, you change the destination it points to.
Thanks.
single case: changed Sticky and SetGID
0030067 /usr/share/ppd/custom
0030067 2007-10-15T11:13:29.000000Z 03775 0 root
108 lpadmin
0030067 2007-10-15T11:13:29.000000Z 0755 0 root
0 root
Maybe ... but why the same timestamp?
First line is 'new', second line is 'old'. So, the same timestamp, group
permissions reduced, but sticky added (as I understand, it is safe),
SetGID added (I did read but I do not understand it very well; together
with reduced group permissions it must be safe).
Mostly, does not looks like hacker/virus activity :)
regards,
Plamen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
