From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,a326ac15995ef20e
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!newsfeed.freenet.de!newsfeed01.chello.at!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Newsgroups: comp.lang.ada
Subject: Re: ANNOUNCE: Debian build scripts on a public Monotone server
From: Georg Bauhaus <bauhaus@futureapps.de>
In-Reply-To: <1159263129.848672.286190@m7g2000cwm.googlegroups.com>
References: <871wpzd7js.fsf@ludovic-brenta.org>
	 <1159259938.13504.19.camel@localhost>
	 <1159263129.848672.286190@m7g2000cwm.googlegroups.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: #
Message-ID: <1159267398.13504.35.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1 
Date: Tue, 26 Sep 2006 12:43:18 +0200
NNTP-Posting-Date: 26 Sep 2006 12:37:05 CEST
NNTP-Posting-Host: 7cfc3167.newsspool3.arcor-online.net
X-Trace: 
 DXC=RSDlVdBQADHX36K@\WTHGJMcF=Q^Z^V3H4Fo<]lROoRA4nDHegD_]RE58cZELRXX`HTiQOITnENoBFU`4:K;4eRGMdh`>L@G`@KMHb]JnH<g2@
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:6750
Date: 2006-09-26T12:37:05+02:00
List-Id: <comp.lang.ada>

On Tue, 2006-09-26 at 02:32 -0700, Ludovic Brenta wrote:


> Monotone needs synchronous communications only during "mtn sync" or its
> two halves, "mtn push" and "mtn pull",

Yes, I meant this kind of synchronous communication.

> I did mention that I required the ability to work off-line on the
> train, didn't I?

You did.

> > (The alternative could be privacy guarded patch emails.)
> 
> A very poor alternative, very work-intensive and error-prone, and
> without support for merging.

I wasn't clear enough about what I mean by "email changeset".
The same content that is needed by mtn sync
could be passed in a mailbox style, decoupling operations.
(Going from rendezvous to something else, in Ada terms.)
I wasn't thinking of sending a standard patch in some email,
I was thinking of using SMTP as a "Monotone sync packet wrapper".
Monotone merging wouldn't have to be changed I think, if you follow
the  "commit first" policy that Monotone recommends.

The GPG keys could be associated with the permission settings in
your Monotone configuration. Then if mtn receives an "email sync
message" the software knows what to do with it, just like when it
operates in "normal synchronous sync mode". 

Just an idea, to overcome some issues:

1/ For mtn sync between two people,
   you need both ends at the same time.
2/ For mtn sync between you and a server,
   you need both ends at the same time.
3/ For 2, you need a server that runs a Monotone server process.

If your ISP/company/... offers 3, that's perfect.


-- Georg