From: Peter Wang <novalazy@gmail.com>
To: Mark Walters <markwalters1009@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v4 0/3] indicate length of omitted body content
Date: Thu, 13 Dec 2012 23:23:36 +1100 [thread overview]
Message-ID: <20121213232336.GA21848@hili.localdomain> (raw)
In-Reply-To: <87vccb2frl.fsf@qmul.ac.uk>
On Sun, 09 Dec 2012 19:21:18 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
>
> Hi (sorry Peter I had assumed git send-email would have cc'd you on my
> rebase earlier today)
>
> There was some discussion about this patch series on irc and the general
> view was favourable but that, for consistency, all omitted parts should
> received a content-length (including text/html). This is a little messy
> to code into the if else stuff: Jani suggested putting
> content-length/content-encoding into a small function.
>
> Anyway I had hope it was just a trivial rebase and could go in, but the
> above will take a bit longer to do neatly so I will leave it for now.
Ok. To save any potential duplicated work: I've updated the patch here,
save for test/sexp. Waiting for that to be pushed before updating it.
Peter
next prev parent reply other threads:[~2012-12-13 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 12:56 [PATCH v4 0/3] indicate length of omitted body content Mark Walters
2012-12-09 12:56 ` [PATCH v4 1/3] test: normalize only message filenames in show json Mark Walters
2012-12-09 12:56 ` [PATCH v4 2/3] show: indicate length, encoding of omitted body content Mark Walters
2012-12-09 12:56 ` [PATCH v4 3/3] test: conform to content length, encoding fields Mark Walters
2012-12-09 19:21 ` [PATCH v4 0/3] indicate length of omitted body content Mark Walters
2012-12-13 12:23 ` Peter Wang [this message]
2012-12-13 12:52 ` Mark Walters
2012-12-13 13:31 ` Peter Wang
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121213232336.GA21848@hili.localdomain \
--to=novalazy@gmail.com \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).