Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269701AbUJAFdz (ORCPT ); Fri, 1 Oct 2004 01:33:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269703AbUJAFdy (ORCPT ); Fri, 1 Oct 2004 01:33:54 -0400 Received: from fw.osdl.org ([65.172.181.6]:38093 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S269701AbUJAFdx (ORCPT ); Fri, 1 Oct 2004 01:33:53 -0400 Date: Thu, 30 Sep 2004 22:29:28 -0700 From: Andrew Morton To: george@mvista.com Cc: juhl-lkml@dif.dk, clameter@sgi.com, drepper@redhat.com, johnstul@us.ibm.com, Ulrich.Windl@rz.uni-regensburg.de, jbarnes@sgi.com, linux-kernel@vger.kernel.org, libc-alpha@sources.redhat.com Subject: Re: patches inline in mail Message-Id: <20040930222928.1d38389f.akpm@osdl.org> In-Reply-To: <415B4FEE.2000209@mvista.com> References: <4154F349.1090408@redhat.com> <41550B77.1070604@redhat.com> <4159B920.3040802@redhat.com> <415AF4C3.1040808@mvista.com> <415B0C9E.5060000@mvista.com> <415B4FEE.2000209@mvista.com> X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1199 Lines: 32 George Anzinger wrote: > > We agree. Still, I have been bitten too many times by misshandled white space > to trust pure inlineing. Likewise on picking it up one would usually past it in > the mail (I suppose) where as the attachment is through the mailer and less > prone to missing a character. > > The best answer, I think, is attachments that show as inline AND stay that way > on the reply. > > Guild lines on how to insure this are welcome. Send angry email to everyone@mozilla.org. AFAICT it's impossible with recent mailnews. Slightly more on-topic: +int do_posix_clock_process_gettime(struct timespec *tp); +int do_posix_clock_process_settime(struct timespec *tp); +int do_posix_clock_thread_gettime(struct timespec *tp); +int do_posix_clock_thread_settime(struct timespec *tp); These should all be given static scope. And it would be nice to structure the code so the forward decl isn't needed, if poss. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/