An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.
One of a set of tools we're offering as a way of saying thank you for being a part of the community.
rlog file - show history with comments (which you entered of course:)
rcs [opts] file: fix things up afterwards (including comments) - read the man page
rcsfreeze - contributed shell script to tag all directory (may not come with rcs)
rcsclean - delete all up_to_date working files (good precaution before distributing RCS dir: shows files you forgot to check in)
Useful Options
============
co -M: Set the modification time on the new working file to be the date of the retrieved revision. Use this option with care; it can confuse make(1).
ci -t- file: Avoids prompt for description of new file (you can put description hard up against -t- if you want)
ci -u -m"comment" file: The way I always use ci. -u keeps a working file in your dir; -m"comment" avoids the prompt for a checkin comment and will apply to multiple files on the command line