bugmonotone - Bugs: bug #12220, tombstones don't make sense

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #12220: tombstones don't make sense

Submitted by:  Nathaniel Smith <njs>
Submitted on:  Sat 05 Mar 2005 10:40:26 AM UTC  
 
Category: networkingSeverity: 1 - Wish
Item Group: code cleanupStatus: Fixed
Privacy: PublicAssigned to: None
Open/Closed: Closed
mtn version --full: 

Mon 16 Jan 2006 01:38:49 AM UTC, comment #1:

tombstones have been removed.

Nathaniel Smith <njs>
Project Member
Sat 05 Mar 2005 10:40:26 AM UTC, original submission:

monotone's merkle trees have the idea of "tombstones", the idea being that such a node is something that we don't have, and don't want. this is a cool idea when one is synchronizing sets, but we're not actually synchronizing sets -- we just use set synchronization as a subroutine in our tree synchronization. masking out certs at the merkle tree level, using tombstones, just doesn't really work as a way to avoid getting revisions.

there has never been any code that let one actually create a tombstone'd node. but there is plenty of code to handle them. this code should be removed, which could lead to significant simplifications in some of the netsync code.

Nathaniel Smith <njs>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Mon 16 Jan 2006 01:38:49 AM UTCnjsStatusNone=>Fixed
  Open/ClosedOpen=>Closed

Back to the top


Powered by Savane 3.1-cleanup1