From: Carl Worth <cworth@cworth.org>
To: Jameson Rollins <jrollins@finestructure.net>, notmuch@notmuchmail.org
Subject: Re: Plans for the 0.2 release (this week)
In-Reply-To: <87vdc2aw6i.fsf@servo.finestructure.net>
References: <8739z6rjxf.fsf@yoom.home.cworth.org>
	<87vdc2aw6i.fsf@servo.finestructure.net>
Date: Tue, 13 Apr 2010 09:06:45 -0700
Message-ID: <87iq7ve3qi.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Thu, 08 Apr 2010 09:52:21 -0400, Jameson Rollins <jrollins@finestructure=
.net> wrote:
> I would really like to see the patch in spaetz/issue15-handle-fcc-bcc
> applied soon.  This is the lingering issue of bcc'ing the primary email
> address in notmuch replies, which I think really needs to be removed.
>=20
> Let me know if there are any issues.  I'm pretty sure this will apply
> cleanly against the head without a rebase.

I'm happy to remove the Bcc thing, but only *after* we have an Fcc
approach integrated into the emacs client by default, (without users
having to configure it, download python scripts, etc.).

And yes, I know the current Bcc approach is still quite useless, because
it only triggers on replies, (and not when composing a new message from
the emacs client).

I'm looking forward to seeing this all fixed, but I haven't yet seen a
"packaged" solution.

=2DCarl

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLxJaV6JDdNq8qSWgRAlbQAJ4woWTTueGTC2nJ8bd3fSE4AoDAggCgnMWo
FsCT9Qzk3XTgc2AZtbfHfK0=
=z2E0
-----END PGP SIGNATURE-----
--=-=-=--