The more I think about the cvs add issue, the less certain I am that
we want to automate it. On the one hand, yes, we've encountered
problems before with people forgetting to cvs add their new files, and I
guess that actually comes up pretty frequently. But on the other hand,
it's convenient to leave files around (especially .txt files like
"comments.txt" for commit comments) in the drjava directory that we
don't want added to the repository. I'd argue at the *least* that we
should only automatically add .java files. I'm willing to concede that
all .java could be added, even though I'm in the habit of having a few
.java files around which I don't intend to commit, either.
Those are my thoughts, anyway... That cvs command you mention is
useful, at any rate.
Charlie
Moez A. Abdel-Gawad wrote:
> For new DrJava hackers (new COMP 312'ers, who would soon be adding
> new unit tests, and possibly new files to DrJava), the following
> pipelined commands may be helpful for knowing which files are new,
> and thus need to be added via "cvs add" to the cvs repository:
>
> cvs -qn update | grep ^? | tr -d '^?' | tr -d "[:space:]"
>
> More details are available at http://ccvs.cvshome.org/fom//cache/42.html
>
> In fact, according to that link, there seems to be some way we can
> automate the "cvs add" in our ant targets, instead of requiring it
> to be done manually.
>
> -Moez
|
