- Aug 20, 2010
-
-
Paolo Giarrusso authored
The problem was introduced already in revision 9f9137cd83f5 by the original Italian translator, according to logs. This might be due to a bug in the program he used, "Lokalize 0.3", or maybe not - some accented characters exist also in that commit.
-
Paolo Giarrusso authored
-
Paolo Giarrusso authored
-
- Aug 18, 2010
-
-
kiilerix authored
Configuration from the outer repo is inherited to the patches repo when --mq is used. In case the patches repo only has paths.default configured but the outer repo has paths.default-push then the inherited default-push will win. Very confusing. Inheriting the default paths is however wrong in all sane cases, so now we explicitly remove them.
-
- Aug 19, 2010
-
-
Dirkjan Ochtman authored
-
- Aug 17, 2010
-
-
Matt Mackall authored
-
Wagner Bruna authored
spotted by Fred Maranhão
-
- Aug 16, 2010
-
-
Wagner Bruna authored
-
Wagner Bruna authored
-
- Aug 13, 2010
-
-
Alecs King authored
Before: hg log --stat -p -r tip # only show stat After: hg log --stat -p -r tip # show stat _and_ diff
-
- Aug 17, 2010
-
-
Martin Geisler authored
-
Martin Geisler authored
-
- Aug 13, 2010
-
-
Dan Villiom Podlaski Christiansen authored
Prior to version 2.7, calling locale.getpreferredencoding() would always return 'mac-roman' on Mac OS X. Previously, this was handled by a call to locale.setlocale(). Unfortunately, Python 2.6.5 and older have a bug where isspace() would incorrectly report True for 0x85 and 0xa0 after such a call. In order to fix this, we replace the previous _encodingfixup mapping to an _encodingfixers mapping. Rather than mapping encodings to their replacement, it maps them to a function returning the replacement. This allows us to provide an simplified implementation of getpreferredencoding() which extracts the expected encoding and restores the locale. This fix is based on a patch originally submitted by Martijn Pieters as well as feedback from Brodie Rao.
-
- Aug 15, 2010
-
-
Patrick Mezard authored
-
- Aug 10, 2010
-
-
Yuya Nishihara authored
It's embeddable in plain javascript, and also conforms to JSON standard.
-
- Aug 13, 2010
-
-
Dan Villiom Podlaski Christiansen authored
Changeset 25e74cd3f023 (from 2008) introduced a hack to handle the very long values of $TMPDIR typically seen on Mac OS X. This hack expected continuation lines to begin with a tab. However, as a result of a change in Python 2.7, changeset 594b98846ce1 made it so continuation lines began with a tab. Since then, `test-notify' has been broken on Mac OS X. Merely replacing the tab in the regular expression with a space will not work: not only do tab continuations still occur in the message, but other lines -- in the body of the message -- also start with a space. Luckily, all broken up lines appear to end with either a colon or an n, so we can match those, and reinsert them in the replacement.
-
- Aug 15, 2010
-
-
Martin Geisler authored
-
Martin Geisler authored
-
- Aug 12, 2010
-
-
Wagner Bruna authored
-
- Aug 15, 2010
-
-
Martin Geisler authored
-
- Aug 14, 2010
-
-
Greg Ward authored
-
- Aug 13, 2010
-
-
kiilerix authored
-
Wagner Bruna authored
On Python 2.6.6 (and patched 2.6.5 on certain Linux distros), the change that caused issue2255 was also applied to non-digest authentication; this change extends the 2ec346160783 fix accordingly.
-
Benoit Boissinot authored
-
- Jul 25, 2010
-
-
Lee Cantey authored
If the temporary directory is longer than /tmp then it's possible that the Subject line will get wrapped by the headencode function.
-
- Aug 13, 2010
-
-
Martin Geisler authored
-
- Aug 12, 2010
-
-
Mark Edgington authored
-
Daniel J. Lauk authored
This test case backs the fix in changeset 7e5f5e5858f9. The subversion sink used to crash, if the source repo used tags.
-
- Aug 13, 2010
-
-
Martin Geisler authored
-
- Aug 12, 2010
-
-
Matt Mackall authored
-
Paolo Giarrusso authored
I started updating many fuzzy messages which no longer expressed the intended meaning - new translations are inserted only to keep coherence. Not all fuzzy messages have been fixed, yet.
-
Paolo Giarrusso authored
Some accented vowels had disappeared.
-
Paolo Giarrusso authored
See http://en.wikipedia.org/wiki/Sentence_spacing to verify that single spacing is indeed correct.
-
- Jul 02, 2010
-
-
Nicolas Dumazet authored
This is a revert of 4a70178f9bde. The "bug" mentioned in this changeset is unclear: hopefully using a test to cover this usage should prevent any bugs.
-
- Aug 11, 2010
-
-
Martin Geisler authored
-
Daniel J. Lauk authored
The convert extension requires puttags(self, tags) to return a sequence for a multi-variable assignment. If puttags implicitly returns None, the code will break when trying to un-pack None for assignment.
-
Martin Geisler authored
This is the style used in the rest of the help strings.
-
Martin Geisler authored
The --only-branch option was deprecated in 0d5f139b23c1 and --branch was added instead. But the graphlog extension was not updated to match the change.
-
- Aug 09, 2010
-
-
kiilerix authored
AIX sh won't delete its own working directory. Removing it from another process works. Also hide the actual OS error message - operating systems returns different errors when getcwd fails.
-
Martin Geisler authored
When the filesystem cannot handle the executable bit, we currently ignore it completely when looking for modified files. Similarly, it is impossible to set or clear the bit when the filesystem ignores it. This patch makes Mercurial treat symbolic links the same way. Symlinks are a little different since they manifest themselves as small files containing a filename (the symlink target). On Windows, these files show up as regular files, and on Linux and Mac they show up as real symlinks. Issue1888 presents a case where the symlink files are better ignored from the Windows side. A Linux client creates symlinks in a working copy which is shared over a network between Linux and Windows clients. The Samba server is helpful and defererences the symlink when the Windows client looks at it. This means that Mercurial on the Windows side sees file content instead of a file name in the symlink, and hence flags the link as modified. Ignoring the change would be much more helpful, similarly to how Mercurial does not report any changes when executable bits are ignored in a checkout on Windows. An initial checkout of a symbolic link on a file system that cannot handle symbolic links will still result in a regular file containing the target file name as its content. Sharing such a checkout with a Linux client will not turn the file into a symlink automatically, but 'hg revert' can fix that. After the revert, the Windows client will see the correct file content (provided by the Samba server when it follows the link on the Linux side) and otherwise ignore the change. Running 'hg perfstatus' 10 times gives these results: Before: After: min: 0.544703 min: 0.546549 med: 0.547592 med: 0.548881 avg: 0.549146 avg: 0.548549 max: 0.564112 max: 0.551504 The median time is increased about 0.24%.
-