[Pkg-xen-devel] SCM and Mailing list input [u]

[Guido Trotter]

On Wed, Feb 15, 2006 at 09:29:54AM -0800, Jeremy T. Bouse [c] wrote:



>     Another option might be to take the upstream hg repository and clone
> for our project, we could then simply pull/update against upstream later
> for upgrades.
> 

But then wouldn't we have the "bloated archive" problem we've notices accessing
the xen repo?

>     The way I figured we'd work with a distributed SCM would be that
> each would clone off the project tree and provide the patches back that
> would get imported into the main tree. We could divide were each
> concentrate thier work on.
> 

That's true, but does the debian package has so many areas of interest that a
simplier system would't be better? (IMHO the less files you have to manage the
easier it is to create conflicts, which would certainly be avoided with a
standard checkout-commit cooperation style...)

>     I had originally thought of not using the full Xen tree, but in
> thinking if it worked better for patch creation then it might not be a
> bad idea.
> 

I would agree if not for the size/speed... For now, though, I still think a
small debian/ directory in subversion would be easier for everybody (including
translators, ecc)...

Guido