<meta name="Description"
content="Open Source Perl for Your Perusement">
<meta name="KeyWords"
- content="reusable, open source, perl, shell, script, recursive, diff, snarf, YETI, free, source code, example, filename, snarfer">
- <title>YETIcode Bash Scripts</title>
+ content="reusable, open source, perl, shell, script, recursive, diff, snarf, yeti, free, source code, example, filename, snarfer">
+ <title>Feisty Meow Concerns Bash Scripts</title>
<meta content="Fred T. Hamster" name="author">
<meta
content="Assorted scripts for enhancing the bash environment and tools that automate fairly common actions."
<tr>
<td>
<center>
- <h1><a href="http://yeticode.org/">YETIcode</a> Open Source Bash
-Scripts</h1>
+ <h1><a href="http://feistymeow.org/">Feisty Meow Concerns</a>Open Source Bash Scripts</h1>
<h2>GPL-Licensed Bash Code<br>
</h2>
</center>
In fact, this file is still in its very first few iterations and is
pretty
limited so far...<br>
- </blockquote>
- <h3> <a href="../rev_control/cvs_importer.sh">cvs_importer.sh</a></h3>
- <blockquote>This script eliminates the need to use the cvs
-import command to pull in a whole new sub-hierarchy. Given a
-sub-folder under an existing hierarchy, it will add all the
-subdirectories and all of the files in those subdirectories. The
-script avoids adding any files found in the internally used CVS
-directories.<br>
-For example, suppose you have a folder called "hoople" that's a
-top-level project in CVS. You want to add a new folder under the
-existing hierarchy "hoople/source/lib_src" called "pasta". The
-"pasta" hierarchy has hundreds of subdirectories and thousands of
-files. Assuming that you've already moved the new pasta source
-folder into place, the command would be:<br>
- cvs_importer hoople/source/pasta<br>
-If you don't have the Yeti aliases set up, then you may need to type
-this instead:<br>
- bash ~/yeti/scripts/cvs_importer.sh
-hoople/source/pasta<br>
</blockquote>
<h3> </h3>
<h3><a href="../database/movie_seeker.sh">movie_seeker.sh</a>