All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Christoph Lameter <clameter@sgi.com>,
	Ulrich Drepper <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
Date: Wed, 29 Sep 2004 17:14:38 -0700	[thread overview]
Message-ID: <415B4FEE.2000209@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0409292143050.2744@dragon.hygekrogen.localhost>

Jesper Juhl wrote:
> Unrelated to the CLOCK_PROCESS/THREAD_CPUTIME_ID discussion, just wanted 
> to comment on the 'patches inline vs attached' bit.
> 
> On Wed, 29 Sep 2004, George Anzinger wrote:
> 
> 
>>Christoph Lameter wrote:
>>
>>>On Wed, 29 Sep 2004, George Anzinger wrote:
>>>
>>>
>>>>Christoph Lameter wrote:
>>>>
>>>>Please, when sending patches, attach them.  This avoids problems with
>>>>mailers,
>>>>on both ends, messing with white space.  They still appear in line, at
>>>>least in
>>>>some mailers (mozilla in my case).
>>>
>>>
>>>The custom on lkml, for Linus and Andrew is to send them inline. I also
>>>prefer them inline. Will try to remember sending attachments when sending a
>>>patch to you.
>>
>>I think they WILL be inline as well as attached if you attach them.  The
>>difference is that in both presentations neither mailer will mess with white
>>space.  This means that long lines will not be wrapped and tabs vs space will
>>not be changed.
>>
> 
> Not all mailers show attachments inline. Mailers that do usually depend on 
> the mimetype of the attachment when choosing to show inline or not. pine 
> (my personal favorite) show attachments with a text/plain and similar 
> mime-type inline, but a not all mailers use that (I see a lot of attached 
> patches on lkml that don't show inline, and that's somewhat annoying).

So we should make sure that the mailer uses the right mime-type.  I suppose that 
depends on the mailer?
> 
> It's also harder to reply and comment on bits of a patch when your mailer 
> does not include attachments inline in a reply (even if it did show them 
> inline while reading the mail).
> Having to save the patch, open it in a text editor and then cut'n'paste 
> bits of it into the reply mail is a pain. Same goes for having to save & 
> open it in order to read it in the first place.

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.
-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  reply	other threads:[~2004-09-30  0:15 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                         ` George Anzinger [this message]
2004-09-30  3:24                           ` patches inline in mail 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
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=415B4FEE.2000209@mvista.com \
    --to=george@mvista.com \
    --cc=Ulrich.Windl@rz.uni-regensburg.de \
    --cc=clameter@sgi.com \
    --cc=drepper@redhat.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 \
    /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.