[Monotone-devel] Re: monotone evaluation in commercial project [long]

[Peter Simons]

Richard Levitte writes:

 >> Is being able to get at this history really so bad a thing?

 > Maybe there is source of embarassment in it?  :-)

That's a good reason. ;-)

Another one is that not all projects are free software, and
not every part of every software is necessarily meant to be
available to everyone. The ability to split a large package
into components (branches) which can exist in various
versions (repositories) and which are kept in sync through
"propagate" is very important to many applications.

Monotone's principal architecture is perfect for dealing
with this setup. The requirement that every repository has
to have the entire ancestry graph, however, doesn't fit
this use pattern very well.

Peter