From e8b0dc8664ff111e82b419dbd0b891caa0735ad1 Mon Sep 17 00:00:00 2001 From: Distix listener Date: Wed, 8 Feb 2017 15:40:10 +0100 Subject: imported mails --- .../Maildir/new/1486564806.M555006P3994Q1.hrun | 109 +++++++++++++++++++++ 1 file changed, 109 insertions(+) create mode 100644 tickets/182bd772889544d5867e1a0ce4e76652/Maildir/new/1486564806.M555006P3994Q1.hrun (limited to 'tickets') diff --git a/tickets/182bd772889544d5867e1a0ce4e76652/Maildir/new/1486564806.M555006P3994Q1.hrun b/tickets/182bd772889544d5867e1a0ce4e76652/Maildir/new/1486564806.M555006P3994Q1.hrun new file mode 100644 index 0000000..ada92a7 --- /dev/null +++ b/tickets/182bd772889544d5867e1a0ce4e76652/Maildir/new/1486564806.M555006P3994Q1.hrun @@ -0,0 +1,109 @@ +Return-Path: +X-Original-To: distix@pieni.net +Delivered-To: distix@pieni.net +Received: from bagpuss.pepperfish.net (bagpuss.pepperfish.net [148.251.8.16]) + (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) + (No client certificate requested) + by pieni.net (Postfix) with ESMTPS id 1DB4C2730D + for ; Wed, 8 Feb 2017 15:39:26 +0100 (CET) +Received: from platypus.pepperfish.net (unknown [10.112.100.20]) + by bagpuss.pepperfish.net (Postfix) with ESMTP id A3030CE2; + Wed, 8 Feb 2017 14:39:25 +0000 (GMT) +Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net) + by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) + id 1cbTP3-0001xC-Hp; Wed, 08 Feb 2017 14:39:25 +0000 +Received: from inmail0 ([10.112.100.10] helo=mx0.pepperfish.net) + by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) + id 1cbTP2-0001wz-5L + for ; Wed, 08 Feb 2017 14:39:24 +0000 +Received: from suhail.uberspace.de ([185.26.156.24] ident=bHvES2bCVHe) + by mx0.pepperfish.net with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) + (Exim 4.80) (envelope-from ) id 1cbTP0-0004nL-6Y + for obnam-dev@obnam.org; Wed, 08 Feb 2017 14:39:24 +0000 +Received: (qmail 18616 invoked by uid 651); 8 Feb 2017 14:39:14 -0000 +Received: from p5DD71318.dip0.t-ipconnect.de (p5DD71318.dip0.t-ipconnect.de + [93.215.19.24]) by htjn.suhail.uberspace.de (Horde Framework) with HTTPS; + Wed, 08 Feb 2017 15:39:14 +0100 +Date: Wed, 08 Feb 2017 15:39:14 +0100 +Message-ID: <20170208153914.Horde.8I6VxN_xeXtgEJeXW_MAMnm@htjn.suhail.uberspace.de> +From: Jan Niggemann +To: obnam-dev@obnam.org +References: <20170121144532.lxn3alp4he4nvrwy@exolobe3> + <87shnoapcg.fsf@euler.schwinge.homeip.net> +In-Reply-To: <87shnoapcg.fsf@euler.schwinge.homeip.net> +User-Agent: Horde Application Framework 5 +Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes +MIME-Version: 1.0 +Content-Disposition: inline +X-Pepperfish-Transaction: ca83-94c0-d782-b97d +X-Spam-Score: -0.7 +X-Spam-Score-int: -6 +X-Spam-Bar: / +X-Scanned-By: pepperfish.net, Wed, 08 Feb 2017 14:39:24 +0000 +X-Spam-Report: Content analysis details: (-0.7 points) + pts rule name description + ---- ---------------------- -------------------------------------------------- + -0.5 PPF_USER_AGENT User-Agent: exists + 0.5 PPF_RECEIVED_HTTP Received header mentions http + 0.2 PPF_REFERENCES_NODOTS References contains no dots after the @ + -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% + [score: 0.0000] + -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no + trust [185.26.156.24 listed in list.dnswl.org] + 1.0 URIBL_RED Contains an URL listed in the URIBL redlist + [URIs: codesourcery.com] +X-ACL-Warn: message may be spam +X-Scan-Signature: 909e24a621a695a51ad00ecc17e68015 +Subject: Re: Obnam FORMAT GREEN ALBATROSS status and roadmap +X-BeenThere: obnam-dev@obnam.org +X-Mailman-Version: 2.1.5 +Precedence: list +List-Id: Obnam development discussions +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +Sender: obnam-dev-bounces@obnam.org +Errors-To: obnam-dev-bounces@obnam.org + + +Zitat von Thomas Schwinge : + +> Hi Lars! +> +> On Sat, 21 Jan 2017 16:45:32 +0200, Lars Wirzenius wrote: +>> I intend to get the new Obnam repository format, GREEN ALBATORSS, +>> finished this year. +> +> :-) +> +> +> One idea I just had -- but I don't know if that is feasible to implement: +> you could (internally!) have obnam "write" both the "current" and the +> "Green Albatross" formats, and then every "read" operation would read +> both of them, and compare that they return the same data. Then have +> obnam complain if that doesn't match (with the "current" format's data +> then taking precedence, I think). Obviously, that will add a lot of +> overhead for every repository access, but any users willing to take that +> can then easily help testing the "Green Albatross" format. But I don't +> know if the repository abstraction in obnam is sufficiently generic for +> being able to deal with two underlying repository formats, etc. +That's exactly what I started doing a couple of weeks ago - I backup +to a repo using the current stable format and then re-run the same +backup using GREEN ALBATROSS... +I don't take measurements though, I just wanted to know how the new +format "feels like"... + +Jan + +-- +gpg --keyserver pgp.mit.edu --recv-keys 0x514FCA9C +F013 93C0 306C 1E31 4E00 09FA 21EC A2F6 514F CA9C + +_______________________________________________ +obnam-dev mailing list +obnam-dev@obnam.org +http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org -- cgit v1.2.1