plugin to reweave history, inserting ghosts

[Jan Hudec]

On Wed, Oct 26, 2005 at 18:30:12 +1000, Martin Pool wrote:
> On 26/10/05, Jan Hudec <bulb at ucw.cz> wrote:
> > On Wed, Oct 26, 2005 at 18:02:45 +1000, Martin Pool wrote:
> > > One goal we want to support in bazaar-ng is "skeleton" or "ghost"
> > > revisions (or some other ghoulish name).  This is where a revision
> > > knows some other revision has been merged, but it doesn't know
> > > anything else about it.  This is supported by tla and baz 1.x, but not
> > > by many other systems.  (It's hard or impossible to do in a system
> > > that identifies versions by hashes.)
> >
> > Is it? You just have a parent hash and don't have that hash in the
> > store. That's a ghost revision. Not that any of mercurial, git or
> > monotone could create it.
> 
> You may not *know* the hash or contents of the parent at the time you
> create the child; this occurs all the time in arch.  You only know the
> id.

I commented on the text in parenthesis -- that the fact it identifies
versions by hashes is irrelevant when it comes to whether it can have
ghost revisions or not.

> > But there is one more version control system that _can_ have ghost
> > revisions - svk. Similarly to arch it does propagate merge information
> > to other repositories, but does not (and can not) propagate the
> > changesets per se.
> 
> Yes, svk could do this as far as I know.  I didn't say no other
> systems could do it.

No. I added it to stress that arch/bazaar are not so special in this
respect.

--
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051026/5a82dc70/attachment.pgp