All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Nicolas Pitre <nico@cam.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	lkml <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>, jgarzik <jgarzik@pobox.com>
Subject: Re: [PATCH/RFC] doc: about email clients for Linux kernel patches
Date: Tue, 11 Sep 2007 20:46:33 +0200	[thread overview]
Message-ID: <20070911184632.GR3563@stusta.de> (raw)
In-Reply-To: <alpine.LFD.0.9999.0709111428490.21186@xanadu.home>

On Tue, Sep 11, 2007 at 02:31:16PM -0400, Nicolas Pitre wrote:
> On Tue, 11 Sep 2007, Adrian Bunk wrote:
> 
> > On Tue, Sep 11, 2007 at 02:03:34PM -0400, Nicolas Pitre wrote:
> > > On Tue, 11 Sep 2007, Randy Dunlap wrote:
> > >...
> > > > +Alpine (TUI)
> > > > +
> > > > +<I don't know.  Maybe Adrian or Linus can comment.>
> > > > +
> > > > +Are any special config options needed?
> > > 
> > > Alpine is the successor of Pine.  Issues that were found in some earlier 
> > > Pine versions wrt patch sending are now fixed.
> > >...
> > 
> > There were no problems with sending patches in pine.
> 
> One old version did have problems with spaces at the end of lines 
> despite the config option, and you had to manually patch it if your 
> distro didn't.

This could be, but it's not worth documenting that there once was one 
broken version.

Generally, pine doesn't have problems with sending patches.

> Nicolas

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-09-11 18:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 17:16 [PATCH/RFC] doc: about email clients for Linux kernel patches Randy Dunlap
2007-09-11 17:36 ` Peter Zijlstra
2007-09-11 18:38   ` Lee Revell
2007-09-11 18:52     ` Peter Zijlstra
2007-09-12  5:07       ` WANG Cong
2007-09-11 22:05     ` Sami Farin
2007-09-12  3:40   ` Randy Dunlap
2007-09-11 18:03 ` Nicolas Pitre
2007-09-11 18:17   ` Adrian Bunk
2007-09-11 18:31     ` Nicolas Pitre
2007-09-11 18:46       ` Adrian Bunk [this message]
2007-09-11 19:09     ` Jan Engelhardt
2007-09-11 19:08   ` Jan Engelhardt
2007-09-11 18:29 ` Adrian Bunk
2007-09-12  5:24   ` WANG Cong
2007-09-12  5:55     ` Adrian Bunk
2007-09-12 15:02       ` Randy Dunlap
2007-09-12 15:43         ` Adrian Bunk
2007-09-11 19:37 ` Chris Friesen
2007-09-11 19:42   ` Martin Bligh
2007-09-11 19:55   ` Jeff Garzik
2007-09-12  3:26     ` Chris Friesen
2007-09-12 18:08       ` Jan Engelhardt
2007-09-12 18:17         ` Chris Friesen
2007-09-12 22:35           ` Stefan Richter
2007-09-12 19:16     ` Rik van Riel
2007-09-12 19:53       ` Peter Zijlstra
2007-09-12 23:09         ` Adrian Bunk
2007-09-11 19:54 ` Stefan Richter

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=20070911184632.GR3563@stusta.de \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=randy.dunlap@oracle.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.