Return-Path: <xxxxx@gmail.com>
Received: from [10.0.3.40] ([199.87.83.38])
by mx.google.com with ESMTPSA id mz4sm36338028pbc.28.2014.11.17.19.17.12
for <T2617+26185+d9372d30f3880f25@phabricator.com>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 17 Nov 2014 19:17:12 -0800 (PST)
From: Tal Shiri <xxxxx@gmail.com>
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: [Maniphest] [Closed] T2617: Process Remarkup in text and HTML email bodies appropriately
Message-Id: <88BA0752-25A2-4925-BBF4-156C45C6D643@gmail.com>
Date: Mon, 17 Nov 2014 19:17:11 -0800
References: <maniphest-task-PHID-TASK-sh4q5i45p2ytzeqzexel@phabricator.com> <00000149c0e66499-57701efe-b91e-4f29-8baf-fe485c46506b-000000@email.amazonses.com>
In-Reply-To: <00000149c0e66499-57701efe-b91e-4f29-8baf-fe485c46506b-000000@email.amazonses.com>
To: "T2617+26185+xxxxxxxx@phabricator.com" <T2617+26185+xxxxxxxx@phabricator.com>
X-Mailer: iPhone Mail (12B411)
This is super awesome.
> On Nov 17, 2014, at 7:16 PM, epriestley (Evan Priestley) <noreply@phabrica=
tor.com> wrote:
>=20
> epriestley closed this task as "Resolved".
> epriestley added a comment.
>=20
> This basically works; we'll probably have a long tail of improving specifi=
c rules or dealing with client weirdness but we can deal with those as they a=
rise.
>=20
>=20
> TASK DETAIL
> https://secure.phabricator.com/T2617
>=20
> REPLY HANDLER ACTIONS
> Reply to comment or attach files, or !close, !claim, !unsubscribe or !ass=
ign <username>.
>=20
> To: lpriestley, epriestley
> Cc: vrana, epriestley, mvuinc, jordan_rose, staticshock, hach-que, qgil, p=
ixelpapst, joshuaspence, igorgatis, taoqiping, cburroughs, chad, talshiri, r=
ush898, timor