[darcs-users] Per-directory version control

Kenneth Knowles kknowles at uclink.berkeley.edu
Wed Mar 3 18:49:01 UTC 2004

Ok, so we actually did (and now do again) agree on exactly your situation.
Aside from splitting hairs on whether we are "exporting a directory" or
"including a subproject", I think we mostly agree. 

I call all files included in a project "sources" (including README's, etc) so
that we can describe the situation more easily.  Using my vocabulary foo-project
and bar-language both have sources outside of the foo subdirectory.  Bar's just
happen to be compiled, whereas foo-project's are distribution errata.
> A good example of this is the Linux kernel.
>  ALSA, DRI, ...

The more you describe, the more I feel this as a good solution.

The alsa/dri maintainers would set up their project like this:

/sources/kernel/alsa/_darcs (points to alsa projects 'src' subproject)

If you did this for every directory, you would have something like CVS, and it
would be pretty gross, Gives me a chill to think about it... 

> > 	"Any set of sources which varies independently should have its own
> > 	patch
> > 	log."
> But, in my case, it wouldn't.

How about this:

	"Any set of sources which varies independently from anyone's perspective
	should have its own patch log."

More information about the darcs-users mailing list