public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linux-kernel@vger.kernel.org, Emeric Dupont <emeric.dupont@zii.aero>
Subject: Re: [PATCH v3] mfd: tqmx86: IO controller with i2c, wachdog and gpio
Date: Thu, 31 Jan 2019 10:23:15 +0000	[thread overview]
Message-ID: <20190131102315.GK4701@dell> (raw)
In-Reply-To: <20190130155227.GC15050@lunn.ch>

On Wed, 30 Jan 2019, Andrew Lunn wrote:

> > > Hi Lee
> > > 
> > > I posted a new version.
> > > 
> > > Your email indicates you are using Mutt:
> > > 
> > > >User-Agent: Mutt/1.9.4 (2018-02-28)
> > > 
> > > Which is also what i use. I've never had issues with signatures like
> > > this. I also cannot find any documentation as to how you configure
> > > mutt remove signatures. How are you doing it?
> > 
> > I think it's automatic.  I certainly didn't set that up.
> 
> Interesting. My mutt installation does not do this. I trim emails
> manually to be netiquette compliant.
> 
> > Try replying to your own mail.  I should automatically cut.
> 
> Replying to my patch works fine. It does not cut the patch.
> 
> This is a bug somewhere, since the marker i used is not a signature
> marker. It did not have the space on the end.

Yes, you're correct, it should be "-- \n".  Give me a sec ...

Ah, it's an Emacs Post-Mode thing:

 ;;; Revision 1.6.0 1999/03/04 18:04 Rob Reid
 ;;; Returned post-signature-pattern to using "--" instead of "-- "
 ;;; because some senders have broken MTAs (as Eric reminded me) and
 ;;; some users don't use procmail to compensate.  This time all of the
 ;;; functions dealing with signatures have been smartened up to avoid
 ;;; false matches.  Unfortunately that means they don't use
 ;;; post-signature-pattern in its raw form.

> Anyway, getting the patch reviewed is more important to me than
> tracing down the bug...

Agreed.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2019-01-31 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 23:56 [PATCH v3] mfd: tqmx86: IO controller with i2c, wachdog and gpio Andrew Lunn
2019-01-29 11:35 ` Lee Jones
2019-01-29 20:56   ` Andrew Lunn
2019-01-30 12:50     ` Lee Jones
2019-01-30 15:52       ` Andrew Lunn
2019-01-31 10:23         ` Lee Jones [this message]

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=20190131102315.GK4701@dell \
    --to=lee.jones@linaro.org \
    --cc=andrew@lunn.ch \
    --cc=emeric.dupont@zii.aero \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox