>> That's what I figured. Well, I need it for a project so I guess you all
>> won't mind if I code it and submit a patch ;)
>>
>> How does --revisions=XXX sound. --revisions=0 would be unlimited, any other
>> number would be the limiter for the number of revisions.
>
>And when it reaches that number, do you want it to delete old
>revisions, or stop making new revisions?
You would delete the old one as you continue rolling down.
>Perhaps something like --backup=numeric would be a better name. In
>the long term it might be better to handle this with scripting.
I don't see a good scripting solution to this. The closest I could come up
with was using the --backup-dir and then remerging the tree after the copy
and that is a real cluge. The scripting solution I see would be to clean
up if you had the backup copys set to unlimited so you don't run out of
disk space.
-Sean
