[tomboy-list] using revisions with Erik Torsner and Perry Trinier PHP code.
sanfordarmstrong at gmail.com
Wed Feb 18 15:18:41 PST 2009
(Don't forget to reply-all, CC'ing list)
Tomboy sync treats the top-level manifest.xml as the "correct" one, and
assumes that if there are later rev directories than they must represent
failed sync attempts. This should only really happen if you lose your
connection to the server in the middle of a sync, or if some sort of
error occurs in Tomboy (I don't know of any common ones at this point).
If your top-level manifest.xml does not appear to be up-to-date, then
something has been going wrong during sync. Let me know if this is
really the case and we can troubleshoot your situation.
On 02/18/2009 02:19 PM, Dan Baker wrote:
> I've had problems with the top level manifest.xml not being the latest
> revision. Will double-check this behavior as it might well be specific
> to my situation.
> Looking forward to reading the tomboy-web code over the next few days
> and hopefully will be able to contribute something useful.
> 2009/2/18 Sandy Armstrong <sanfordarmstrong at gmail.com
> <mailto:sanfordarmstrong at gmail.com>>
> On 02/18/2009 12:36 PM, Dan Baker wrote:
> I was expecting the behavior to be that 0/manifest.xml would
> always be
> the latest revision, but this doesn't currently seem to be the
> case. I
> have to look inside the folder of the latest revision and read the
> manifest from there... eg, 0/6/manifest.xml
> There's also a top-level manifest.xml that is identical to the one
> in the latest rev directory. That is the one you should use, as it's
> possible that the highest-numbered rev directory is actually a
> botched sync attempt that will be cleaned up on the next sync (the
> whole reason we do the separate directory revision thing).
More information about the Tomboy-list