Regarding cvsignore the Cederqvist manual says
"The per-repository list in `$CVSROOT/CVSROOT/cvsignore' is appended to
the list, if that file exists."
currently, my $CVSROOT/CVSROOT dir does not contains a cvsignore file. Is
it sufficient to simply create the file in the directory,
or do I nee
Greg,
Thanks for your response. My general feeling all along was that this is a
bad idea. But, my co-worker is adamant, and I really didn't have much in
the way of a response for him when he asked "why is it a bad idea?"
> CVS is not suited for derived files no matter what their internal
Hello all, I have been having an interesting discussion with a co-worker,
and am looking for some additional thoughts. My organization is just
adopting CVS, and source code management. ( don't even ask how we did it
in the past, you don't wanna know ). Anyway, we have been discussing
exactly
Hello all, I was wondering if some of you nice people could give me some
feedback on an issue I've been wrestling with.
Besides the actual source code to a project, I also need the ability to
version design documentation ( and maybe other stuff, but this is my
immediate concern ). By design doc
Hi, just wondering if there are any DT developers on the list, who use CVS
to manage your Rexx code? If so, I was wondering how other people manage
their DT projects. Due to the nature of DT, it's most convenient to use
your x:\dtalk directory as your working directory, in a sense, because
that's
> When a Linux user goes a checkout of a module, all the files are
> writeable and they stay that way even after a commit. When a Windows
> user, however, does a checkout via WinCVS, all the files are read-only.
> Is there a way to make them writeable via WinCVS? Also, when the files
> are