Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
On Thu, 14 Jun 2007 11:15:36 -0300, Gerhard Fiedler <lists at connectionbrazil.com> wrote: >I have (admittedly rare) applications for removing past (obsolete) >revisions. It seems that I'm not the only one, as the "select non >significant" revisions command in WinCvs seems to show: someone took the >effort to implement it, and its main purpose seems to be to remove these >revisions after selecting them. > There are a few items in admin that are handy at least for me: 1) Modifying the log message if it has been mistakenly copied from the previous commit in WinCvs. Happens now and then and is misleading in future reading of the logs. 2) When one stores binaries (like we do), the principle is that normally only tagged releases should be committed. But this tends to be forgotten and a large number of intermediate unusable binaries (exe file for instance) get committed. THis in turn leads to the RCS file growing to a very large size on the server, which then leads to the slowing down of cvs operations on that module. If you consider that, an admin command that simply cuts away a number of non-useful intermediate binaries is really handy to reduce the RCS file size. HTH /Bo (Bo Berglund, developer in Sweden)