From: Teemu Likonen <tlikonen@iki.fi>
To: Junio C Hamano <gitster@pobox.com>
Cc: Reece Dunn <msclrhd@googlemail.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Gnus content transfer encoding (was: [PATCH 1/4] sha1-lookup: add new "sha1_pos" function to efficiently lookup sha1)
Date: Sun, 05 Apr 2009 23:28:22 +0300 [thread overview]
Message-ID: <87r60626c9.fsf_-_@iki.fi> (raw)
In-Reply-To: <7vocvaq36x.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sun\, 05 Apr 2009 13\:02\:30 -0700")
On 2009-04-05 13:02 (-0700), Junio C Hamano wrote:
> Reece Dunn <msclrhd@googlemail.com> writes:
>> I think Junio is trying to learn base64 :)!
>
> I think that is what my Gnus/message-mode did. I do not know which
> letter triggered it to decide it is UTF-8 to begin with, though. As
> far as I am aware, I didn't type anything non-ascii in my message.
You can customize the encoding decision mechanism, for example:
(setq mm-body-charset-encoding-alist
'((iso-8859-1 . 8bit)
(utf-8 . 8bit)))
For more info, see:
C-h v mm-body-charset-encoding-alist RET
next prev parent reply other threads:[~2009-04-05 20:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 20:59 [PATCH 1/4] sha1-lookup: add new "sha1_pos" function to efficiently lookup sha1 Christian Couder
2009-04-05 10:17 ` Sverre Rabbelier
2009-04-05 14:41 ` Jeff King
2009-04-05 14:42 ` Sverre Rabbelier
2009-04-05 18:59 ` Junio C Hamano
2009-04-05 19:06 ` Sverre Rabbelier
2009-04-05 19:59 ` Jeff King
2009-04-05 20:05 ` Sverre Rabbelier
2009-04-05 19:19 ` Felipe Contreras
[not found] ` <87vdpi29a4.fsf@iki.fi>
2009-04-05 19:30 ` Felipe Contreras
2009-04-05 19:31 ` Reece Dunn
2009-04-05 20:02 ` Junio C Hamano
2009-04-05 20:25 ` Jeff King
2009-04-05 20:35 ` Sverre Rabbelier
2009-04-05 20:28 ` Teemu Likonen [this message]
2009-04-06 0:30 ` Gnus content transfer encoding Junio C Hamano
2009-04-05 20:39 ` [PATCH 1/4] sha1-lookup: add new "sha1_pos" function to efficiently lookup sha1 Reece Dunn
2009-04-05 20:17 ` Jeff King
2009-04-05 20:34 ` Jay Soffian
2009-04-05 13:11 ` Johannes Schindelin
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=87r60626c9.fsf_-_@iki.fi \
--to=tlikonen@iki.fi \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=msclrhd@googlemail.com \
--cc=srabbelier@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.