From: Vincent Li <macli@brc.ubc.ca>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan.kim@gmail.com>,
riel@redhat.com, fengguang.wu@intel.com, linux-mm@kvack.org
Subject: Re: [RESEND][PATCH V1] mm/vsmcan: check shrink_active_list() sc->isolate_pages() return value.
Date: Tue, 8 Sep 2009 11:32:45 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0909081106490.24907@kernelhack.brc.ubc.ca> (raw)
In-Reply-To: <20090907083603.2C74.A69D9226@jp.fujitsu.com>
On Mon, 7 Sep 2009, KOSAKI Motohiro wrote:
> > > [ Sending Preferences ]
> > > [X] Do Not Send Flowed Text
> > > [ ] Downgrade Multipart to Text
> > > [X] Enable 8bit ESMTP Negotiation (default)
> > > [ ] Strip Whitespace Before Sending
> > >
> > > And Documentation/email-clients.txt have:
> > >
> > > Config options:
> > > - quell-flowed-text is needed for recent versions
> > > - the "no-strip-whitespace-before-send" option is needed
> > >
> > > Am I the one to blame? Should I uncheck the 'Do Not Send Flowed Text'? I
> > > am sorry if it is my fault.
> >
> > Ah, I quoted the pine Config options, the alpine config options from
> > Documentation/email-clients.txt should be:
> >
> > Config options:
> > In the "Sending Preferences" section:
> >
> > - "Do Not Send Flowed Text" must be enabled
> > - "Strip Whitespace Before Sending" must be disabled
>
> Can you please make email-clients.txt fixing patch too? :-)
Sorry my poor written English make you confused.:-). The two config
options for alpine are already in email-clients.txt and I followed the existing config options
recommendation. I am not sure if my alpine is the faulty email client. Is
there still something missing with alpine?
>
>
> >
> > and my alpine did follow the recommendations as above showed.
> >
> > I used 'git send-email' to send out the original patch.
>
>
>
>
Vincent Li
Biomedical Research Center
University of British Columbia
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-09-08 18:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 23:49 Vincent Li
2009-09-03 21:06 ` Andrew Morton
2009-09-03 22:02 ` Vincent Li
2009-09-03 22:47 ` Andrew Morton
2009-09-04 21:39 ` Vincent Li
2009-09-04 23:53 ` Andrew Morton
2009-09-08 13:21 ` Mel Gorman
2009-09-08 22:39 ` Vincent Li
2009-09-08 23:27 ` Minchan Kim
2009-10-15 22:47 ` Vincent Li
2009-10-15 23:13 ` Vincent Li
2009-10-16 2:10 ` Minchan Kim
2009-10-16 2:20 ` Wu Fengguang
2009-10-16 3:05 ` KOSAKI Motohiro
2009-10-16 3:26 ` Vincent Li
2009-11-26 4:56 ` KOSAKI Motohiro
2009-09-09 9:59 ` Mel Gorman
2009-09-04 1:37 ` Minchan Kim
2009-09-04 2:01 ` Andrew Morton
2009-09-04 5:01 ` Vincent Li
2009-09-04 16:05 ` Vincent Li
2009-09-06 23:38 ` KOSAKI Motohiro
2009-09-08 18:32 ` Vincent Li [this message]
2009-09-08 23:47 ` KOSAKI Motohiro
2009-09-09 12:04 ` Johannes Weiner
2009-09-09 13:22 ` Minchan Kim
2009-09-22 21:02 ` Andrew Morton
2009-09-22 23:01 ` Vincent Li
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=alpine.DEB.2.00.0909081106490.24907@kernelhack.brc.ubc.ca \
--to=macli@brc.ubc.ca \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox