Re: suggestion for making cvs updates one step easier
Actually adding it to .cvsignore does not change the behavior of 'cvs update', it will still download MANIFEST after 'make clean' has deleted it. sorry for so much trouble about a piece of trivia. i'm perfectly capable of understanding the makefile and reading up on CVS enough to fully understand what's going on. after I do that, i might suggest something, but meantime just forget about this detail. "K" == Kai wrote: K "Matt Swift" [EMAIL PROTECTED] writes: as i said, because i don't want "make clean" to delete anything that "cvs update" will download after it's deleted. K Oh, sorry. I completely forgot to mention that I have `cvs remove'd K the file and added it to .cvsignore. Therefore, it will be treated K just like the *.elc files -- not added to CVS, not updated. K kai K -- K I like BOTH kinds of music. --
Re: suggestion for making cvs updates one step easier
On 08 Jun 2000, Matt Swift [EMAIL PROTECTED] wrote: Actually adding it to .cvsignore does not change the behavior of 'cvs update', it will still download MANIFEST after 'make clean' has deleted it. It needs to be removed from CVS as well. Consider that done. :) Daniel -- The youth gets together his materials to build a bridge to the moon, or, perchance, a palace or temple on the earth, and, at length, the middle-aged man concludes to build a woodshed with them. -- Henry David Thoreau
Re: suggestion for making cvs updates one step easier
Matt Swift [EMAIL PROTECTED] writes: In tramp, does "make clean" really need to remove the file MANIFEST? I think MANIFEST should go in .cvsignore and be removed from the CVS server, since it is automatically generated from the Makefile. What do you think? kai -- I like BOTH kinds of music.
