From: Ryan Harper <ryanh@us.ibm.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: [PATCH] xm: cleanup sched-sedf and tests
Date: Mon, 13 Mar 2006 10:03:23 -0600 [thread overview]
Message-ID: <20060313160323.GH14363@us.ibm.com> (raw)
In-Reply-To: <20060313155346.GI2928@leeni.uk.xensource.com>
* Ewan Mellor <ewan@xensource.com> [2006-03-13 09:54]:
> On Mon, Mar 13, 2006 at 09:36:48AM -0600, Ryan Harper wrote:
>
> > I'll be sure to use hg export. I thought that inline was preferred rather
> > than attachment so that the patch is readable directly in the mail client.
> > Ideally, the patch shouldn't word-wrap. I can make them attachments if
> > that is the preferred method.
>
> I've heard people say that they prefer inline, but for me, an attachment is by
> far the best option. My client (mutt) can show attachments inline anyway, so
> reading the patch is not a problem, but cut-and-pasting from the terminal
> certainly can be.
Agreed. Now if we can fix the mail clients that send patches as
application/octet-stream with don't get auto-inlined. =)
> Patches do have a tendency to word-wrap. Many developers work right up to the
> 80th column, which means that by the time you add the two characters on the
> left for the diff indicators, you're going to wrap. Furthermore, the headers
> on the diff often include a full path name and a date, and they wrap most of
> the time.
Yep.
> If you want to cover all bases, you can attach it _and_ paste it inline, but
> I'd be happy just with the attachment. There are a few conscientious people
> who do that, but I don't want to put too much burden on those people doing
> good work for Xen, and I certainly wouldn't insist upon it!
OK.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2006-03-13 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 23:42 [PATCH] xm,xend: flesh out xm sched-sedf Ryan Harper
2006-03-10 0:39 ` Ewan Mellor
2006-03-10 20:06 ` [PATCH] xm: cleanup sched-sedf and tests Ryan Harper
2006-03-10 23:35 ` [PATCH] Fix Makefile.am for -> " Daniel Stekloff
2006-03-11 14:51 ` Ewan Mellor
2006-03-13 15:36 ` Ryan Harper
2006-03-13 15:53 ` Ewan Mellor
2006-03-13 16:03 ` Ryan Harper [this message]
2006-03-13 16:31 ` Ewan Mellor
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=20060313160323.GH14363@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=ewan@xensource.com \
--cc=xen-devel@lists.xensource.com \
/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.