Re: Proposal for collaborative maintenance of packages
On Tue, 20 Dec 2005, J. Bruce Fields wrote:
> On Tue, Dec 20, 2005 at 03:32:42PM -0200, Henrique de Moraes Holschuh wrote:
> > On Tue, 20 Dec 2005, J. Bruce Fields wrote:
> > > On Tue, Dec 20, 2005 at 08:47:44AM -0200, Henrique de Moraes Holschuh wrote:
> > > > Since bzr (and other arch derivates) have the benefit of NEVER forgeting
> > > > which changesets are in a tree, I prefer them over any other distributed
> > > > system. If anyone knows of other distributed system that saw the light and
> > > > implemented this, please let me know.
> > >
> > > What's an example of a VCS that does forget changesets? I'm not sure I
> > > understand the requirement.
> > I never said it was a requirement.
> > Examples are: all VCSes that do not track every changeset by an unique
> > identifier which is not changed even when the changeset is migrated across
> > repositories, and all VCSes that lose track of component changesets across
> > merges.
> Have you looked at mercurial or git? I think they both do that.
> Monotone too, I assume.
Yes, they do, I just checked it. Thanks! git is not a VC, though, but it
has its uses.
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot