On Fri, Jun 13, 2008 at 12:28 PM, Ian Dexter R. Marquez
<[EMAIL PROTECTED]> wrote:
> The beauty of RCS is it's native to the OS (at least in the multiple
> OS and distros I'm handling), and there's no need to install other
> packages or binaries. Also useful are `rcsdiff`, `rlog`, and their
> cohor
RCS?
1. Create an RCS directory in the "folder" you want to put under
version control. Better if it's a symlink to a different location, not
under the same "folder".
2. ci -u [files]
3. co -l [files] # when you want to use them
4. Lather, rinse, repeat.
The beauty of RCS is it's native to the OS
On Tue, Jun 10, 2008 at 1:32 PM, Ludwig Isaac Lim <[EMAIL PROTECTED]> wrote:
> Hi:
>
>Hi! I'm planning to put a certain folder under a version control system.
> The files under the
> folder a combination of .sh (bourne shell), .ksh (korn shell) and .pl (perl)
> files. As stated in
> the title
both will do although i am partial to SVN for my personal repositories while in
the project (due to lack of a more competent resource) i am administering the
CVS repository. what the SVN doc basically says is that it is able to track
directory versions (rename, delete, addition) while CVS cannot s
Hi:
Hi! I'm planning to put a certain folder under a version control system.
The files under the
folder a combination of .sh (bourne shell), .ksh (korn shell) and .pl (perl)
files. As stated in
the title of the email most of these files are not related (e.g. changes to
file1.sh will not
af
5 matches
Mail list logo
