Lars:
> Larry McVoy <lm@bitmover.com> said:
> > Thanks, we agree completely. It's actually an impossible problem
> > for a program since it requires semantic knowledge of the content
> > under revision control.
>
> So, another option would be to have the developer define explicit
>dependencies
> for his changesets, but I fear that might prove to cumbersome, too.
>
If you spend the effort to do _that_, you might as well clone your BK
tree and prune it back to a state which conceivably has only the
changes which you depend on.
Another problem with that approach, however, is that if everybody
does it then the kernel's version tree, as evident in "bk revtool",
gets totally unreadable. It is already an order of magnitude too
complicated. :-(
-- Matthias Urlichs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 23 2002 - 22:00:43 EST