It looks as if your *actual* problem is figuring how to motivate one employee to get in the version control loop. Allow me to suggest some possible motivation techniques:
- Money talks
- If you are management, or can get management's backing offer to hire an intern who's job it is to simply check his code in for 1/2 the intern's salary. (ie. he's giving up half the intern's salary out of his own salary).
- If you aren't management, offer to check his code in for him at $15 per instance, payable before checkin.
- If he's not going to check things in correctly anyway, make it a process. He FTP's the files to the test server, someone else tests his code, provides feedback and if successful, the tester checks in the code
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||