comment on

Just to note, one of the design goals of Subversion was that the command interface be backwards-compatible with CVS. So if you switch over, you won't need to relearn how to use your SCM, just remember to type 'svn' instead of 'cvs' (or alias cvs=svn in a shell startup file). The only thing you need to get used to is that you are now able to rename and move directories, as well as do a bunch of other stuff :-).

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

In reply to Re^3: Learning How to Use CVS for Personal Perl Coding Practices by tirwhan
in thread Learning How to Use CVS for Personal Perl Coding Practices by neversaint

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks