On Fri, Sep 22, 2006 at 03:42:47PM -0500, John Goerzen wrote:
> That doesn't work so well for heavily distributed systems such as darcs.
> In darcs, every repo is a branch, and every branch is a repo. Every
> repo represents exactly 1 branch. Of course, branching is cheap, so
> creating repos is also cheap.
I'm a casual user of distributed VCS (used sparingly hg and baz here),
but I don't see how this is related to the field as we are intending it.
But maybe it's just because I'm not that familiar with them, let me know
if this is the case.
AFAICT, no matter how may repo you're pulling changes from or pushing
changes to, you as a DD have a main repository out of which you create
the debian package, isn't it? That's probably the repo the user want to
see, e.g. the one where you've just committed (or pulled, it doesn't
matter) the fix which triggered the +pending tag in the BTS.
As a different point, the distinction upstream/debian does not always
apply. All my packages maintained with svn doesn't have an upstream
part, I just use an orig tarball (some times available on the repo,
sometimes no) and the mergeWithUpstream property.
Cheers.
--
Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy
zack@{cs.unibo.it,debian.org,bononia.it} -%- http://www.bononia.it/zack/
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. -!-
Attachment:
signature.asc
Description: Digital signature