From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7850 invoked from network); 9 Jan 2009 16:30:40 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.2.5 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 9 Jan 2009 16:30:40 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 88239 invoked from network); 9 Jan 2009 16:30:35 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 9 Jan 2009 16:30:35 -0000 Received: (qmail 23934 invoked by alias); 9 Jan 2009 16:30:28 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 26268 Received: (qmail 23921 invoked from network); 9 Jan 2009 16:30:28 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 9 Jan 2009 16:30:28 -0000 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by bifrost.dotsrc.org (Postfix) with ESMTP id 3469F802720C for ; Fri, 9 Jan 2009 17:30:24 +0100 (CET) Received: by fg-out-1718.google.com with SMTP id e21so3314190fga.37 for ; Fri, 09 Jan 2009 08:30:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=z+8rqN7NgitrclWtilt8X6cno9iSMDTQnDINRkGvbh8=; b=GuQisjDUvTsT9UMJdZVu0PikdJ9VHz7rjUW/yq2VVfDj+5X+WsupXhuShCYkglWgh+ Ixn5Bq24Jjlk5Pa9nPz7n52hpWBRkWc+eYyGiY83CEFEV8o5ugz+NLo8k0R2JSfkVesr IH2+wSl6T/iuHk6nHkdwsO0I/e20pAqTyDDIY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=V1soCJUZo+ucGSx67UVaiHQmPh9fgE6GJ8nwezCq7cl+t7maItGuM1cSn6HrdW3SRa 5w9uw1JcfJHOrtzv7PVvv9/klcBngqDziX+h1zEYgQ9Sm6ag+cdnuT25gC6MsaMlx3h7 kttEauPKla+9+NQQV9IeQg3kv7P4UWYRSQvt8= Received: by 10.86.100.19 with SMTP id x19mr14978829fgb.18.1231518624462; Fri, 09 Jan 2009 08:30:24 -0800 (PST) Received: by 10.86.62.8 with HTTP; Fri, 9 Jan 2009 08:30:24 -0800 (PST) Message-ID: <2d460de70901090830s77bbb789p6190a0f2822544ed@mail.gmail.com> Date: Fri, 9 Jan 2009 17:30:24 +0100 From: "Richard Hartmann" To: "Bart Schaefer" Subject: Re: [Patch] define-composed-chars mistake, additions Cc: zsh-workers@sunsite.dk In-Reply-To: <090109080136.ZM1522@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2d460de70901090118y4e2926e8g61bf0aaca8bc12f6@mail.gmail.com> <090109080136.ZM1522@torch.brasslantern.com> X-Virus-Scanned: ClamAV 0.92.1/8848/Fri Jan 9 14:16:38 2009 on bifrost X-Virus-Status: Clean On Fri, Jan 9, 2009 at 17:01, Bart Schaefer wrote: > Actually in most cases I'd personally rather that the patch be inline, > unless it's really large. It makes it easier to search for in the > zsh.org mailing list archives, and nobody seems to agree on what MIME > type to use for attached patches. Inline stuff can be affected by line breaks and other crap, though. If you want, I can start sending my patches both inline & attached, though. Richard