Christian Ebert <blacktrash@gmx.net> [Thu, 16 Oct 2008 17:08:46 +0200] rev 7117
Document email.charsets in hgrc.5
hgrc.5.ja.txt probably should include an example like:
[email]
charsets = iso-8859-1, iso-8859-15, windows-1252, iso-8859-2,
windows-1250, iso-2022-jp, iso-2022-jp-ms
Christian Ebert <blacktrash@gmx.net> [Sat, 12 Jul 2008 19:12:18 +0100] rev 7116
notify: mime-encode messages
- addresses will be properly encoded
- message bodies will also be encoded as we are not sending
patches that are meant to be applied
- update test output
- adapt test-keyword to ignore the new headers
Christian Ebert <blacktrash@gmx.net> [Sat, 12 Jul 2008 19:12:10 +0100] rev 7115
patchbomb: mime-encode headers and parts not containing patches
Do nothing for "hg email --test" to preserve display.
Christian Ebert <blacktrash@gmx.net> [Sat, 12 Jul 2008 19:11:59 +0100] rev 7114
mail: add methods to handle non-ascii chars
- headencode, addressencode: encode headers
- mimeencode: encode message parts not containing patches
- new email config "charsets"
Users may configure email.charsets as a list of charsets they
consider appropriate for the recipients of their outgoing mails.
Conversion is tried in this order:
1. us-ascii
(ascii, us-ascii are removed from email.charsets if present)
2. email.charsets (if present) in order given
3. util._fallbackencoding, util._encoding, utf-8
if not already in email.charsets
Mads Kiilerich <mads@kiilerich.com> [Fri, 17 Oct 2008 21:26:39 +0200] rev 7113
mq: Allow qrefresh --silent to take parameters
'hg qrefresh --short file.txt' now adds changes made to file.txt to current
patch.
This builds on a patch for implementing --amend by Kirill Smelkov as discussed
in issue933.
FIXME: Why do mq refresh have two matchers if we only need one?
"Hiroshi Funai" <hfunai@gmail.com> [Sat, 18 Oct 2008 03:53:54 -0500] rev 7112
[PATCH 2 of 2] Re: created hgweb theme - monoblue
Hiroshi Funai <hfunai@gmail.com> [Thu, 09 Oct 2008 02:52:22 +0900] rev 7111
added monoblue hgweb theme
Bernhard Leiner <bleiner@gmail.com> [Fri, 17 Oct 2008 01:05:10 +0200] rev 7110
Add parseindex2.py test case
Make sure that the new implementation in C return that same values as the
original Python implementation.
Bernhard Leiner <bleiner@gmail.com> [Fri, 17 Oct 2008 00:24:22 +0200] rev 7109
use the new parseindex implementation C in parsers
Bernhard Leiner <bleiner@gmail.com> [Fri, 17 Oct 2008 01:03:38 +0200] rev 7108
C implementation of revlog index parsing