git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Jay Soffian" <jaysoffian@gmail.com>
Cc: git@vger.kernel.org, "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 1/3] mailinfo: ensure handle_filter gets only one line at a time
Date: Fri, 15 Feb 2008 22:22:47 -0800	[thread overview]
Message-ID: <7vir0pe7yg.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vmyq1e86n.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 15 Feb 2008 22:17:52 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> The function is intended to be fed one logical line at a time to
> inspect, but a QP encoded raw input line can have more than one
> lines, just like BASE64 encoded one.
>
> Quoting LF as =0A may be unusual but RFC2045 allows it.

Well, this is a bit dark-gray.

The canonical line ending CRLF should not be represented as =0A
and the intention of RFC2045 seems to allow =0A only as part of
binary contents.  So strictly speaking this may not be needed,
but there may always be not quite conforming MUA that would
break the assumption and would bite us, so we'd better be safe
than sorry.

  reply	other threads:[~2008-02-16  6:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 21:53 [PATCH 1/3] mailinfo: ensure handle_filter gets only one line at a time Jay Soffian
2008-02-15 21:53 ` [PATCH 2/3] mailinfo: support rfc3676 (format=flowed) text/plain messages Jay Soffian
2008-02-15 21:53   ` [PATCH 3/3] test mailinfo rfc3676 support Jay Soffian
2008-02-15 23:24 ` [PATCH 1/3] mailinfo: ensure handle_filter gets only one line at a time Junio C Hamano
2008-02-15 23:37   ` Jay Soffian
2008-02-16  6:17     ` Junio C Hamano
2008-02-16  6:22       ` Junio C Hamano [this message]
2008-02-16  6:51       ` Jay Soffian

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=7vir0pe7yg.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@gmail.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;
as well as URLs for NNTP newsgroup(s).