On 2009-07-26, Don Bruder <[email protected]> wrote ... > In article <[email protected]>, > [email protected] wrote:
>> But, here's what I can't answer: if I want to edit that file again, do I >> have to check it back _out_, before editing it? When I do 'cvs checkout >> <filename>', I get a message that the module can't be found. Two >> questions: > Which means that you COULD "checkout" exactly once, make so many changes > that the original code isn't recognizable, never "commit", and still be > good to go - at least in your working directory. The Repository codebase > might go off in some other direction completely, but until/unless you > update from the repository, or commit your changes, you can behave as if > you're the only person working on the code. (Which is one of the major > ideas that drove the creation of the CVS system to begin with...) Remainder of response snipped. Thank you: that was very clear, and I understand it a lot better now. May I ask another question? I have a load of shell scripts in $HOME/bin... nothing fancy, just some shit that I've knocked together over the years to do various menial crap that I can't be bothered remembering the various switches to. Now I want to add them to cvs, but what do I do with the files in $HOME/bin ? They need to stay there, as my $PATH points there. When an 'import' is done, are the files in $HOME/bin copied to $CVSROOT, a la 'ln -s'? In short, do I need to do.. $ cd $HOME/bin $ cvs import -m "my shell scripts" me bin * $ rm -rfv $HOME/bin $ cvs checkout bin ..? Wouldn't that recreate the appropriate files in $HOME/bin, and I could edit, commit and update at will? Do I *need* to delete them at all? Can't I just .. $ cd $HOME/bin $ cvs import -m "my shell scripts" me bin * $ cvs checkout bin .. and then forget about it, except when I alter one of the files? (not too sure yet about the syntax of my above commands.. )
