No subject

this is sufficient to force foo to be its own project - which is an onus on the
foo-project maintainers, but not much of one.  Conceptually it may bother you,
but I think the whole issue of who imports and who exports the directory falls
away if you imagine subprojects being non-interactively, automatically pulled,
recorded, pushed, etc...

> In fact, the whole problem is that that subdirectory *doesn't* change 
> independantly, yet it has to be maintained as if it *did* change 
> independantly. 

Exactly!  Without the "subproject" command/concept in darcs, this is true, and
is the right solution.  But with subprojects, there is no additional
maintanence, just setup...  I'm feeling pretty far afield, because I have no
projects that work like this, and I may be missing subtleties.  Anything else?

Kenn