Mercurial > hg > mercurial-crew-with-dirclash
view contrib/win32/mercurial.ini @ 1950:5f581f337b05
hgk "committer:" bug
I've been having an hgk problem with this tree:
http://xenbits.xensource.com/ext/linux-ppc-2.6.hg, specifically changeset
93c590d23a53.
The problem seems to be that the commit message contains a "committer:" line,
which triggers a (relatively unused?) case in hgk.py... Both cases need the
dates at the end of the line.
author | Hollis Blanchard <hollisb@us.ibm.com> |
---|---|
date | Wed, 15 Mar 2006 03:19:16 +0100 |
parents | 2dc06dd76ff4 |
children | 45235e492cc6 |
line wrap: on
line source
; System-wide Mercurial config file. To override these settings on a ; per-user basis, please edit the following file instead, where ; USERNAME is your Windows user name: ; C:\Documents and Settings\USERNAME\Mercurial.ini ; By default, we try to encode and decode all files that do not ; contain ASCII NUL characters. What this means is that we try to set ; line endings to Windows style on update, and to Unix style on ; commit. This lets us cooperate with Linux and Unix users, so ; everybody sees files with their native line endings. [extensions] ; The win32text extension is available and installed by default. It ; provides built-in Python hooks to perform line ending conversions. ; This is normally much faster than running an external program. hgext.win32text = [encode] ; Encode files that don't contain NUL characters. ** = cleverencode: ; Alternatively, you can explicitly specify each file extension that ; you want encoded (any you omit will be left untouched), like this: ; *.txt = dumbencode: [decode] ; Decode files that don't contain NUL characters. ** = cleverdecode: ; Alternatively, you can explicitly specify each file extension that ; you want decoded (any you omit will be left untouched), like this: ; **.txt = dumbdecode: