[PATCH 0/5] Store message modification times in the DB

2011-12-20 Thread Austin Clements
Quoth David Edmondson on Dec 20 at 8:32 am: > > == Two-way "merge" from host R to host L == > > > > Per-host state: > > - last_mtime: Map from remote hosts to last sync mtime > > With the proposed changes it seems that the state required on each host > would live within the Xapian database (to b

[PATCH 0/5] Store message modification times in the DB

2011-12-20 Thread David Edmondson
On Mon, 19 Dec 2011 14:48:21 -0500, Austin Clements wrote: > Here are sketches for two sync algorithms with different properties. > I haven't proven these to be correct, but I believe they are. In > both, R is the remote host and L is the local host. They're both > one-way (they only update tags

Re: [PATCH 0/5] Store message modification times in the DB

2011-12-20 Thread Tom Prince
On Mon, 19 Dec 2011 14:48:21 -0500, Austin Clements wrote: > This protocol requires significantly more state, but can also > reconstruct per-tag changes. Conflict resolution is equivalent to > what git would do and is based solely on the current local and remote > state and the common ancestor st

Re: [PATCH 0/5] Store message modification times in the DB

2011-12-20 Thread Austin Clements
Quoth David Edmondson on Dec 20 at 8:32 am: > > == Two-way "merge" from host R to host L == > > > > Per-host state: > > - last_mtime: Map from remote hosts to last sync mtime > > With the proposed changes it seems that the state required on each host > would live within the Xapian database (to b

Re: [PATCH 0/5] Store message modification times in the DB

2011-12-20 Thread David Edmondson
On Mon, 19 Dec 2011 14:48:21 -0500, Austin Clements wrote: > Here are sketches for two sync algorithms with different properties. > I haven't proven these to be correct, but I believe they are. In > both, R is the remote host and L is the local host. They're both > one-way (they only update tags

[PATCH 0/5] Store message modification times in the DB

2011-12-19 Thread David Edmondson
On Tue, 13 Dec 2011 18:11:40 +0100, Thomas Jost wrote: > This is a patch series I've been working on for some time in order to be > able to sync my tags on several computers. I'm posting it now, but > please consider it as a RFC rather than something that is ready to be > pushed. > > The basic i

[PATCH 0/5] Store message modification times in the DB

2011-12-19 Thread Tom Prince
On Mon, 19 Dec 2011 14:48:21 -0500, Austin Clements wrote: > This protocol requires significantly more state, but can also > reconstruct per-tag changes. Conflict resolution is equivalent to > what git would do and is based solely on the current local and remote > state and the common ancestor st

[PATCH 0/5] Store message modification times in the DB

2011-12-19 Thread Austin Clements
Quoth David Edmondson on Dec 19 at 4:34 pm: > On Tue, 13 Dec 2011 18:11:40 +0100, Thomas Jost > wrote: > > This is a patch series I've been working on for some time in order to be > > able to sync my tags on several computers. I'm posting it now, but > > please consider it as a RFC rather than s

Re: [PATCH 0/5] Store message modification times in the DB

2011-12-19 Thread Austin Clements
Quoth David Edmondson on Dec 19 at 4:34 pm: > On Tue, 13 Dec 2011 18:11:40 +0100, Thomas Jost wrote: > > This is a patch series I've been working on for some time in order to be > > able to sync my tags on several computers. I'm posting it now, but > > please consider it as a RFC rather than some

Re: [PATCH 0/5] Store message modification times in the DB

2011-12-19 Thread David Edmondson
On Tue, 13 Dec 2011 18:11:40 +0100, Thomas Jost wrote: > This is a patch series I've been working on for some time in order to be > able to sync my tags on several computers. I'm posting it now, but > please consider it as a RFC rather than something that is ready to be > pushed. > > The basic id

[PATCH 0/5] Store message modification times in the DB

2011-12-13 Thread Thomas Jost
Hello world, This is a patch series I've been working on for some time in order to be able to sync my tags on several computers. I'm posting it now, but please consider it as a RFC rather than something that is ready to be pushed. The basic idea is to the last time each message was modified, i.e.

[PATCH 0/5] Store message modification times in the DB

2011-12-13 Thread Thomas Jost
Hello world, This is a patch series I've been working on for some time in order to be able to sync my tags on several computers. I'm posting it now, but please consider it as a RFC rather than something that is ready to be pushed. The basic idea is to the last time each message was modified, i.e.