From: Paul M. <pm...@mv...> - 2001-07-03 06:00:38
|
Hi Pete, Nice work on the script. One thing though, I ran into a few issues while I was testing it.. namely, it had some problems forcibly overwriting existing files with the symlink (ie, ln -sf behavior). I talked to Charles Duffy about it, and he suggested something like the attached patch. After applying the patch, everything worked properly for me. Anyways, unless anyone has any issues with the patch, I'll shove it into CVS. On Sun, Jul 01, 2001 at 07:32:44PM -0700, Pete Popov 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. > Regards, -- Paul Mundt <pm...@mv...> MontaVista Software, Inc. |