From: Pete P. <pp...@pa...> - 2001-07-02 16:12:15
|
James Simmons wrote: >>Don't know if this would be useful to anyone else but Paul mentioned a >>similar script that he uses for another drop in tree. This one works for >>me and helps keep the linux-mips tree in a separate directory so I don't >>have cvs problems when updating, committing, etc. The script takes the >>linux-mips tree, the stock kernel tree, and a new development directory >>as inputs. It copies the stock tree to the new dev directory; then it >>recurses through the new dev directory and: >>* renames all files that are in common between the linux-mips and new >>dev tree directories to *.stock >>* creates a link in the new dev directory that points to the file in the >>linux-mips directory. >> >>That way you can develop in the new directory, but you can still easily >>update and commit from within the linux-mips directory. >> > > Could you place that into the top level of CVS. Yes, but it hasn't been tested all that much. > We should have a INSTALL file as well with instructions. I'll try to do a first pass at a short INSTALL file sometime tonight. Pete |