Re: ls*, markup and other things

[Alexey M. <al...@hs...>]

>>>>> "AM" == Alexey Morozov <mo...@no...> writes:

 AM> A while ago my Novosoft bosses (actually it's Marod :-)) told that
 AM> would be fine to have a workaround against one well-known cvs (librcs)
 AM> bottleneck: when file processing time dramatically increases when
 AM> there're long/complicated commit history. One possible solution for
 AM> the problem is to implement (in a separated utility) a kind of
 AM> purge/merge operation. This will allow us to remain compatible w/
 AM> stock cvs and solve some of the problems. The question: is there
 AM> another, more convenient way? Or we should change the repository
 AM> format instead and solve the problem completely?..

Huh?  You mean purging intermediate revisions that are, say, older than
certain date?  This could be done simply with 'cvs admin -o' (an option
inherited from the RCS).


man rcs:

       -orange
              deletes ("outdates") the revisions given by  range.
              A  range  consisting  of  a  single revision number
              means that  revision.   A  range  consisting  of  a
              branch  number  means  the  latest revision on that
              branch.  A range of the form rev1:rev2 means  revi╜
              sions  rev1  to rev2 on the same branch, :rev means
              from the beginning of the branch containing rev  up
              to  and including rev, and rev: means from revision
              rev to the end of the branch containing rev.   None
              of  the  outdated  revisions  can  have branches or
              locks.


Of course, that's maybe kind of extreme to do this, though maybe
practical.


In the long term rewriting of librcs could be considered, surely :) It
could create all sorts of temporary files and indices near the master
,v-file.  I do not think that such decision should be taken lightly, though
it could have a lot of advantages.

--alexm