Re: [linuxsh-dev] Tree Management Questions

[Greg B. <gn...@al...>]

Jeremy Siegel wrote:
> 
> (1) Of the four files to be changed, two aren't in the drop-in tree yet.
> I'm assuming we expect to regularly add/drop files in common areas as
> SH development proceeds,[...]

  I'm certainly expecting that.

> (2) The MTD files are maintained by David in his own CVS; he'd like
> versions in SH (or kernel.org) trees to keep keywords unchanged for
> easy comparison with his tree. [...]

  I have no objection to -ko on MTD source files.  The $Id$ should
really come from the master CVS for the source file; perhaps MR
can add something along these lines to the dev doc?

> [...]I don't mind just
> waiting in this case for the changes to percolate from David to Linus
> to SH...

  I think that would probably be the worst solution.

> [...] (kernel, linux:HEAD,
> linux:linux-2_4-branch) [...] and I don't want to be the one to start the
> disconnect. 

  For "linux:HEAD" vs "linux:linux-2_4-branch", the timing is Linus' job ;-)

  As to whether you should spend time updating "kernel", that depends
on Niibe-san.

> [...] drop-in trees could be made by simply copying the kernel module
> and deleting all the files that weren't needed,[...]

  That would be a *really* good idea if we had shell access to
the CVS machine at sourceforge.  I don't (offhand) know of a way
to copy or remove entire ,v files remotely, but I'd be happy to
have someone explain it to me.

Greg.
-- 
the price of civilisation today is a courageous willingness to prevail,
with force, if necessary, against whatever vicious and uncomprehending
enemies try to strike it down.	   - Roger Sandall, The Age, 28Sep2001.