Re: [linuxsh-dev] Re: [linux-sh:01966] New linux drop-in tree

[M. R. B. <mr...@0x...>]

* Greg Banks <gn...@al...> on Tue, Oct 16, 2001:

>=20
>   Why don't you check this script into CVS, under linux/scripts/ ?
>=20
>   Also, it might be nice to have files which are replaced (rather than
> added) by treelink.sh backed up, so there's something like a mm/vmscan.c.=
orig.
> This saves a lot of futzing about to get per-file diffs later.
>=20

Ok, I've committed the treelink.sh and treeunlink.sh scripts.  treelink.sh
makes symlinks from a drop-in tree within a full kernel tree, and any files
that it modifies it saves in a .orig subdirectory.  So to get diffs within
a directory, use either `diff -u .orig/foo foo` or `diff -u .orig/ .`.

The treeunlink.sh script restores the full kernel tree to the state it was
in before treelink.sh got to it, barring any directories that existed in the
drop-in tree but not in the kernel tree.  I'll fix that later.

Hmm, I haven't yet tried dropping a drop-in tree on top of a drop-in tree
(e.g. `treelink.sh linux-2_4-branch linux-2.4.13-pre2` followed by
`treelink.sh linux-sh-dc linux-2.4.13-pre2`), but I don't see why it
wouldn't work.  treeunlink.sh eradicates all symlinks within the tree, so
you should still be able to fully restore the tree if necessary.

Also, under one or two rare instances vim replaced the symlink with a
regular file, but I don't remember what I was doing, so if anyone runs into
this let me know.

M. R.