From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.224.197 with SMTP id ip5cs58209icb; Thu, 17 Feb 2011 11:59:14 -0800 (PST) Received: by 10.52.161.138 with SMTP id xs10mr451286vdb.185.1297972752830; Thu, 17 Feb 2011 11:59:12 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id e2si1830475vcs.45.2011.02.17.11.59.12; Thu, 17 Feb 2011 11:59:12 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 42CB21678328; Thu, 17 Feb 2011 14:59:12 -0500 (EST) Received: from mail-qw0-f50.google.com (mail-qw0-f50.google.com [209.85.216.50]) by rubyforge.org (Postfix) with ESMTP id CECB618582E2 for ; Thu, 17 Feb 2011 13:45:21 -0500 (EST) Received: by qwd6 with SMTP id 6so2797309qwd.23 for ; Thu, 17 Feb 2011 10:45:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Btc4WJRw2Yl82pYzrjZsWUFMdQL2nHsxTtcZNCBIG4w=; b=eBSSrKyS136KdVZZ55vGMKTYNLyQL1R4DgOE3nvSw6iqhcef6+GmqcSftNe8EtD+Jg qC5xAhAwTaUVXmceEEEU/wSsA8FOlc5qXdipqqJSZPb4tc3JZgMMrL1/SwlrrFsd++PA Pji1xsPDYk3RFMUtkUsjVPVl3v08MJnD3rAiM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=dahEmMPRPtJywmRV7jZpq/QRX6Ho9zqkohw4AP1QV4v/iDG/xsf7ciUu68Z797Pt0D Q0azwAuYj+rygZqxamztiD9FIKgHZm/sdfcEvI+otLosJETteUIFhZNNX6ps0l2og8iX BwrHnc9Gp9Fb8OX+yD+Eq9OjKX9pULnkEhvTY= MIME-Version: 1.0 Received: by 10.224.11.149 with SMTP id t21mr2928967qat.369.1297968320825; Thu, 17 Feb 2011 10:45:20 -0800 (PST) Received: by 10.229.218.79 with HTTP; Thu, 17 Feb 2011 10:45:20 -0800 (PST) In-Reply-To: <1297953902-sup-8049@meteor.durcheinandertal.local> References: <1297953902-sup-8049@meteor.durcheinandertal.local> Date: Thu, 17 Feb 2011 18:45:20 +0000 Message-ID: From: Hamish D To: Sup developer discussion Subject: Re: [sup-devel] GPGME fixes X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org > While reimporting all my messages I encountered a few problemes with > the GPGME code. Please consider the attached fixes. 0001-Encode-multipart-messages-for-crypt-operations.patch already appears to be in master ... I like the others though, though in applying them I ran into some trouble, partly through my adding lines near the top of the file that change line numbers and seemed to confuse git. So they are now applied to a local copy, but in my name (but with your commit messages). I imagine you would like them to be in your name, so I have not pushed them yet. If anyone could tell me how I should be applying them properly then I will do. And maybe it might be necessary to format the patches with options that give more context. I'm hoping someone with more git knowledge than me can help ... Hamish _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel