Re: [linuxsh-dev] Tree Management Questions

[Jeremy S. <js...@mv...>]

"M. R. Brown" wrote:

> No objections, but with your last suggestion (below) it seems that you
> probably would want to wait until we "retrofit" the drop-in tree.

I'll put the stuff in the way I have been; as long as the trees all remain
pretty much in sync (actually, as long as "kernel" doesn't fall behind)
any "retrofit" will not be affected.  (The relief of having it checked in
at all is greater than the burden of doing multiple check-ins!)

> I guess my preference would be to commit to branch and then merge back with
> HEAD, it seems we can do that until we either decide to start moving files
> around in HEAD, or 2.5 hits the streets, whichever comes first.

Seems the way to go when trees separate and you want to move deltas
between branches with CVS doing most of the work!  (As long as they
remain basically the same, I'll probably check both in independently,
and do my own copying and editing.)

> > (4) Chatting with one of our architects here (Marcus, I think you
> > know Gilbert?) about the drop-in trees, I mentioned that I'd asked
> > for the old kernel tree to stay for history purposes since the new
> > linux modules believe last month was the dawn of time.  He thought
> > the drop-in trees could be made by simply copying the kernel module
> > and deleting all the files that weren't needed, resulting in the same
> > (pruned) tree [though with different actual version numbers inside]
> > but with all the old history.  Any thoughts on the value of that?
>
> Wow, that's a great idea!  I've been a bit scarce in the LinuxSH world as
> I'm busy working on a project for MV, but I should at least have some time
> this weekend to complete that, unless you (or someone else) would like to
> get to it before then.

I'll defer to you -- I'm not familiar enough with repository management
to believe I could do it safely.  In the meantime I'll treat all three modules
identically w.r.t. changes so as not to introduce any new differences into
the works.

Thanks!
  --Jeremy