This was what I was thinking too.
I have lot of stuff which is not (yet) added to CVS.
Wouldn't this script delete all those too?
The current cvsclean ONLY deletes the files which are
not in CVS and are mentioned in .cvsignore. Much safer that way.
If there are files that are not mentioned in .c
On Fri, 02 Nov 2001, Markus Fischer wrote:
> I'd expect running cvsclean cleans up the source tree in a
> way it *works like* a fresh cleanout. But I don't want my private
> files floating in the tree (like some private testing c sources,
> some diffs and what else) to be deleted when they don
On Fri, Nov 02, 2001 at 03:15:09PM +0100, Hartmut Holzgraefe wrote :
> i'd expect running cvsclean gives me exactly the set of files
> i'd get from a fresh checkout and nothing more, and that definetly
> isn't the case with the current cvsclean while it is with my
> alternative
I'd expect ru
Jani Taskinen wrote:
> What problems were those? Which files were leftovers which
> didn't get deleted?
can't reproduce now :(
(didn't take a snapshot copy before trying out)
> Just add them to .cvsignore ?
.cvsignore is a negative list, cvsclean should work on a
positive list aka. CVS/Ent
What problems were those? Which files were leftovers which
didn't get deleted? Just add them to .cvsignore ?
I haven't noticed any problems.. :)
(if it ain't broken, don't fix it :)
--Jani
On Fri, 2 Nov 2001, Hartmut Holzgraefe wrote:
>
>i had a closer look at the php4/cvsclean script yesterd
i had a closer look at the php4/cvsclean script yesterday as i was
experiencing some problems when running configure that were clearly
related to left-over files from previous runs
while i thought cvsclean would remove every file not under CVS
control i found in php4/build/build.mk that it only
