All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: alan@lxorguk.ukuu.org.uk, olaf+list.linux-kernel@olafdietsche.de,
	george@mvista.com, akpm@osdl.org, 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,
	Simon.Derr@bull.net
Subject: Re: [OT] Re: patches inline in mail
Date: Sun, 3 Oct 2004 23:20:33 -0700	[thread overview]
Message-ID: <20041003232033.7790445f.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0410032255360.5054@poirot.grange>

Guennadi wrote:
> However, everybody (not pine-users) complains, that white spaces got 
> corrupted. And if I export the email I see ...

I complained about the same extra space to a colleague of mine,
Simon Derr <Simon.Derr@bull.net>.

A day later, Simon wrote back to me:
> I think I found the culprit:
> pine 4.60 and later have a feature about 'flowed text' that has to be
> explicitely turned off and that messes with whitespaces.

And indeed, that fixed his patches, from my perspective.

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373

  parent reply	other threads:[~2004-10-04  6:22 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B6E8046E1E28D34EB815A11AC8CA312902CD3264@mtv-atc-605e--n.corp.sgi.com>
2004-09-24 12:16 ` [time] add support for CLOCK_THREAD_CPUTIME_ID and CLOCK_PROCESS_CPUTIME_ID Christoph Lameter
2004-09-25  4:25   ` Ulrich Drepper
2004-09-25  5:25     ` Christoph Lameter
2004-09-25  5:54     ` Christoph Lameter
2004-09-25  6:08       ` Ulrich Drepper
2004-09-25 14:51         ` Christoph Lameter
2004-09-25 15:19           ` Ulrich Drepper
2004-09-27 15:03             ` Christoph Lameter
2004-09-27 15:34         ` Christoph Lameter
     [not found]         ` <B6E8046E1E28D34EB815A11AC8CA312902CD327E@mtv-atc-605e--n.corp.sgi.com>
2004-09-27 20:58           ` [RFC] Posix compliant behavior of CLOCK_PROCESS/THREAD_CPUTIME_ID Christoph Lameter
2004-09-27 22:54             ` George Anzinger
2004-09-28 19:18             ` Ulrich Drepper
2004-09-28 19:25               ` Christoph Lameter
2004-09-29  3:25               ` Posix compliant CLOCK_PROCESS/THREAD_CPUTIME_ID V4 Christoph Lameter
2004-09-29 17:45                 ` George Anzinger
2004-09-29 18:14                   ` Christoph Lameter
2004-09-29 19:27                     ` George Anzinger
2004-09-29 19:34                       ` Christoph Lameter
2004-09-29 19:52                       ` Jesper Juhl
2004-09-30  0:14                         ` patches inline in mail George Anzinger
2004-09-30  3:24                           ` Paul Jackson
2004-10-01  5:29                           ` Andrew Morton
2004-10-01 12:28                             ` Alan Cox
2004-10-01 13:42                               ` Paul Fulghum
2004-10-01 19:53                                 ` Lee Revell
2004-10-01 21:58                               ` George Anzinger
2004-10-02 15:52                                 ` Olaf Dietsche
2004-10-02 15:20                                   ` Alan Cox
2004-10-03 21:01                                     ` [OT] " Guennadi Liakhovetski
2004-10-03 23:18                                       ` Jesper Juhl
2004-10-04  6:20                                       ` Paul Jackson [this message]
2004-10-04 19:11                                         ` Guennadi Liakhovetski
2004-10-04  7:26                                       ` Ulrich Windl
2004-10-03 21:35                                     ` George Anzinger
2004-10-04  3:00                                       ` Jim Nelson
2004-10-01  9:04                           ` Jesper Juhl
2004-09-29 19:32                   ` Posix compliant CLOCK_PROCESS/THREAD_CPUTIME_ID V5 Christoph Lameter
2004-10-01 19:57                   ` Posix compliant cpu clocks V6 [0/3]: Rationale and test program Christoph Lameter
     [not found]                   ` <B6E8046E1E28D34EB815A11AC8CA31290322B307@mtv-atc-605e--n.corp.sgi.com>
2004-10-01 19:59                     ` Posix compliant cpu clocks V6 [1/3]: Generic Kernel patch Christoph Lameter
2004-10-01 21:03                       ` Andrew Morton
2004-10-01 20:01                     ` Posix compliant cpu clocks V6 [2/3]: Glibc patch Christoph Lameter
2004-10-02  5:32                       ` Ulrich Drepper
2004-10-04 15:04                         ` Christoph Lameter
2004-10-04 16:27                         ` Christoph Lameter
2004-10-06 13:53                         ` Martijn Sipkema
2004-10-01 20:02                     ` Posix compliant cpu clocks V6 [3/3]: mmtimer provides CLOCK_SGI_CYCLE Christoph Lameter
2004-10-07  4:56                     ` Posix compliant cpu clocks V7 [0/2]: Rationale and test program Christoph Lameter
2004-10-12 20:19                       ` Periodic posix timer support broke between 2.6.9-rc1 and 2.6.9-rc1-bk17 Christoph Lameter
2004-10-12 22:24                         ` George Anzinger
2004-10-13 18:08                         ` Alexander Nyberg
2004-10-13 18:11                           ` Christoph Lameter
     [not found]                     ` <B6E8046E1E28D34EB815A11AC8CA31290322B331@mtv-atc-605e--n.corp.sgi.com>
2004-10-07  4:57                       ` Posix compliant cpu clocks V7 [1/2]: Kernel Patch Christoph Lameter
2004-10-07  4:59                       ` Posix compliant cpu clocks V7 [2/2]: Glibc patch Christoph Lameter
2004-10-21 19:32               ` Posix compliant process clock patch for the linux arch in glibc Christoph Lameter
2004-10-01 21:57             ` [RFC] Posix compliant behavior of CLOCK_PROCESS/THREAD_CPUTIME_ID Roland McGrath
2004-10-01 23:30               ` Christoph Lameter
2004-10-04 18:48               ` RFC: Posix compliant clock_getclockcpuid(pid) to access other processes clocks Christoph Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041003232033.7790445f.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=Simon.Derr@bull.net \
    --cc=Ulrich.Windl@rz.uni-regensburg.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=clameter@sgi.com \
    --cc=drepper@redhat.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=george@mvista.com \
    --cc=jbarnes@sgi.com \
    --cc=johnstul@us.ibm.com \
    --cc=juhl-lkml@dif.dk \
    --cc=libc-alpha@sources.redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf+list.linux-kernel@olafdietsche.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.