If you presented this to them as a private exchange between you and
them, not representing a community, I agree.

If you think publishing it, or even talking to them about publishing it
will make them nervous (which would be understandable), it might be
better to avoid doing that, and only send it to people requesting it,
with an understanding about its limited circulation.

Daniel

Cees de Groot <cg at cdegroot.com> wrote:
> 
> --Boundary_(ID_zsLPazWmpr509C+suwFHgw)
> Content-type: multipart/signed; boundary="=-rUfZ1RL6NBnGlSHZ1tao";
>  protocol="application/pgp-signature"; micalg=pgp-sha1
> 
> 
> --=-rUfZ1RL6NBnGlSHZ1tao
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
> 
> On Thu, 2003-03-27 at 16:37, Daniel Vainsencher wrote:
> > If there are reasons against posting this publically [...]
> 
> The biggest reason of course is that one shouldn't willy-nilly publish
> private email exchanges. I'll try to insert a request for permission to
> share the thread with the public in one of my next mails to Apple.
> 
> 
> 
> --=-rUfZ1RL6NBnGlSHZ1tao
> Content-Type: application/pgp-signature; name=signature.asc
> Content-Description: This is a digitally signed message part
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> 
> iD8DBQA+g0WL8wOTf+CYnosRAp88AJ9gIHJJxhjD986Lci8ctK3KC1hadwCdHBIC
> 0+Qt+zmnShLxhZTXJ4aUEDY=
> =YSNm
> -----END PGP SIGNATURE-----
> 
> --=-rUfZ1RL6NBnGlSHZ1tao--
> 
> 
> --Boundary_(ID_zsLPazWmpr509C+suwFHgw)
> MIME-version: 1.0
> Content-type: text/plain; charset=us-ascii
> Content-transfer-encoding: 7BIT
> 
> 
> 
> --Boundary_(ID_zsLPazWmpr509C+suwFHgw)--