summaryrefslogtreecommitdiffstats
path: root/sbin/adjkerntz/adjkerntz.c
diff options
context:
space:
mode:
authorjoerg <joerg@FreeBSD.org>1995-03-26 21:56:32 +0000
committerjoerg <joerg@FreeBSD.org>1995-03-26 21:56:32 +0000
commit4522c9df34373401f2b1cf77f4e58a961137d2de (patch)
treead6bdbd2991ddb35365fa297fd07413c832041fb /sbin/adjkerntz/adjkerntz.c
parent24d628f8ae3f37ecb8621cea25dabfe9e52c2543 (diff)
downloadFreeBSD-src-4522c9df34373401f2b1cf77f4e58a961137d2de.zip
FreeBSD-src-4522c9df34373401f2b1cf77f4e58a961137d2de.tar.gz
Made this script a bit more fool-proof, so people like me can better
use it. :-) It now explicitly requires the specification of a directory to import from, either as an argument to the script, or by asking the user about it. (Previously, it implicitly used `.', like cvs import does.) Also implemented an option `-n', which does essentially the same like the overall CVS option `-n': show only what would have been done, don't do any commitment. Note that since the modules' database is checked out in place (and not commited back), it will erroneously be reported as to be imported, too: cvs import: Importing /home/ncvs/ports/foobar/foo/modules I ports/foobar/foo/modules/CVS N ports/foobar/foo/modules/modules This is an unwanted side-effect, but gives the user the option to see if the `ed' magic did the right thing when editing modules/modules. Rod, can you please check the function ``checktag'' in the script if it will be restritctive enough?
Diffstat (limited to 'sbin/adjkerntz/adjkerntz.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud