[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "cvs commit" features
From: |
Greg A. Woods |
Subject: |
Re: "cvs commit" features |
Date: |
Wed, 9 Oct 2002 13:18:29 -0400 (EDT) |
[ On Wednesday, October 9, 2002 at 07:41:59 (+0200), Reinstein, Shlomo wrote: ]
> Subject: "cvs commit" features
>
> 1. An option to make "commit" ask you if you'd like to get rid of files that
> exist in the repository but not in your working directory, and possibly
> specify on the command-line which files to remove (or have the "commit" ask
> you for each file or for each file extension).
If you're already writing wrapper scripts then one to do that is nearly
trivial to write using 'cvs -nq update'.
> 2. An option to make "commit" ask you if you'd like to add files that exist
> in your working directory but not in the repository, and possibly specify on
> the command-line which files to add (or have the "commit" ask you for each
> file or for each file extension).
Once again that's an almost trivial wrapper script to write.
> Of course, a user can always use "cvs add" and "cvs remove" to add or remove
> files,
Indeed one can and one should.
> but these two options can help him/her make sure they didn't forget
> to do this for some of the files.
No, not really. Think of the CVS sub-commands as verbs for your wrapper
scripts and use them that way. You don't want complex verbs that
confuse the meaning of what's really going on.
--
Greg A. Woods
+1 416 218-0098; <address@hidden>; <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>