- May 12, 2016
-
-
Katsunori FUJIWARA authored
Before this patch, "hg help topic.section" might show unexpected section of help topic in some encoding. It applies str.lower() instead of encoding.lower(str) on translated message to search section case-insensitively, but some encoding uses 0x41(A) - 0x5a(Z) as the second or later byte of multi-byte character (for example, ja_JP.cp932), and str.lower() causes unexpected result. To search section of help topic by translated section name correctly, this patch replaces str.lower() by encoding.lower(str) for both query string (in commands.help()) and translated help text (in minirst.getsections()).
-
Katsunori FUJIWARA authored
Before this patch, patch.filterpatch() shows meaningless translation of help message for chunk selection in some encoding. It applies str.lower() instead of encoding.lower(str) on translated message, but some encoding uses 0x41(A) - 0x5a(Z) as the second or later byte of multi-byte character (for example, ja_JP.cp932), and str.lower() causes unexpected result. To show lower-ed translated message correctly, this patch replaces str.lower() by encoding.lower(str).
-
- May 09, 2016
-
-
Matt Harbison authored
It previously aborted saying the help section wasn't found. Credit to Yuya for figuring out the fix.
-
- May 06, 2016
-
-
Sean Farley authored
This is needed so that launchpad and friends have a unique version number for each distroseries (trusty, wily, xenial, etc). It was discovered when trying to upload 3.8 to launchpad.
-
- May 01, 2016
-
-
Sean Farley authored
-
Sean Farley authored
Debian maintainers already have this and lintian warns us about not listing 'wish' as a dependency or suggestion so this patch does indeed just that. The issue, by the way, is that we are shipping hgk (which is written in tcl/tk) so we should be good citizens and list wish (a meta package for tcl/tk) as a dependency.
-
- May 07, 2016
-
-
Sean Farley authored
This corrects a warning from lintian that we're shipping an executable without a man page. Since there is a doc string in the text, let's use that for the man page.
-
- May 06, 2016
-
-
Matt Mackall authored
The progress bar was being cleared on every write(), regardless of whether it was currently displayed. This could foul up the display of any writes that didn't include a linebreak. In particular, the win32 mode of the color extension was turning single prompt string writes into two writes, and the resulting clear/write/clear/write pattern was making the prompt invisible. We fix this by insisting that we have shown a progress bar and haven't just cleared it (setting lastprint to 0). Conveniently, the test suite already had instances of duplicate clears.. that are now cleared up.
-
- May 05, 2016
-
-
Pierre-Yves David authored
Regular users are not supposed to be exposed to the API deprecation warnings. We now only issue them when the developper warnings are enabled.
-
Augie Fackler authored
This corrects a regression introduced during the 3.7 cycle, but which went undetected due to the surviving-but-deprecated write() method on bmstore.
-
Augie Fackler authored
This hasn't been testing anything since partway through the 3.7 cycle due to unrelated refactoring. Sadly, the behavior it was trying to prevent reemerged in the codebase at that time. A fix is in the next patch, because proving that the fix was actually correct ended up being trickier than I expected.
-
Mike Hommey authored
getbundle was requesting the "phase" namespace instead of the "phases" namespace, which led to the client still requesting the phases separately after getbundle finished.
-
- May 01, 2016
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- Apr 07, 2016
-
-
Blake Burkhart authored
Fixes CVE-2016-3105 (1/1). Previously, it was possible for the repository path passed to git-ls-remote to be misinterpreted as a URL. Always passing an absolute path to git is a simple way to avoid this.
-
- May 01, 2016
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Sean Farley authored
-
Sean Farley authored
It seems this is correct but does it work on older distros? I ran the docker-jessie rule and didn't get any warnings.
-
Sean Farley authored
It turns out we just need debian/rules to be executable, so we do just that.
-
- Apr 30, 2016
-
-
Sean Farley authored
Apparently, this is needed to allow ppas to be built for multiple distros.
-
Pierre-Yves David authored
Before this patch, `hg pull --rebase` would be a strict sequence of `hg pull` followed by `hg rebase` if anything was pulled. Now that rebase pick his default destination the same way than merge, than `hg rebase` step would abort in the case the repo already had multiple anonymous heads (because of the ambiguity). (changed in fac3a24be50e) The intend of the user with `hg pull --rebase` is clearly to rebase on pulled content. This used to be (mostly) enforced by the former default destination for rebase, "tipmost changeset of the branch" as the tipmost would likely a changeset that just got pulled. But this intended was no longer enforced with the new defaul destination (unified with merge). This changeset makes use of the '_destspace' mechanism introduced in the previous changeset to enforce this. This partially fixes issue5214 as no change at all have been made to the new handling of the case with bookmark (unified with merge).
-
Pierre-Yves David authored
In the 'hg pull --rebase', we don't want to pick a rebase destination unrelated to the pull, we lay down basic infrastructure to allow such restriction on stable (before 3.8 release) in this case. See issue 5214 for details. Actual usage and test will be in the next patch.
-
Gregory Szorc authored
This effectively backs out changeset 1fde84d42f9c. The http library behind ui.http2=true isn't specifying the hostname. It is the day before the expected 3.8 release and we don't want to ship a regression. I'll try to restore this requirement in the 3.9 release cycle as part of planned improvements to Mercurial's SSL/TLS interactions.
-
- Apr 28, 2016
-
-
Matt Mackall authored
We've historically had a problem maintaining the expected invariants on our caches, especially when introducing new caches. This tests documents the invariants and exercises them across most of our existing cache files.
-
Matt Mackall authored
The atomictemp.close() file attempts to do a rename, which can fail. Moving the close inside the exception handler fixes it. This doesn't fit well with the with: pattern, as it's the finalizer that's failing.
-
Matt Mackall authored
tryread() doesn't handle "is a directory" errors and presumably others. We might not want to globally swallow such tryread errors, so we replace with our own try/except handling. An upcoming test will use directories as a portable stand-in for various bizarre circumstances that cache read/write code should be robust to.
-
Matt Mackall authored
Follow our standard STFU cache-handling pattern
-
- May 01, 2016
-
-
Wagner Bruna authored
-
- Apr 27, 2016
-
-
Sean Farley authored
-
Sean Farley authored
-
Sean Farley authored
-
Sean Farley authored
-
Sean Farley authored
-
Sean Farley authored
This allows us to easily add more ubuntu docker targets (which following patches will do). Also, we no longer need the mkdir command.
-
Sean Farley authored
-
- Apr 28, 2016
-
-
Adam Simpkins authored
Properly shell quote arguments, to avoid printing commands that won't work when run literally. For example, a date string with timestamp needs to be quoted: --date '1456953053 28800'
-
- Apr 29, 2016
-
-
Kevin Bullock authored
-
- Apr 27, 2016
-
-
Kevin Bullock authored
Instead of using bdist_mpkg, we use the modern Apple-provided tools to build an OS X Installer package directly. This has several advantages: * Avoids bdist_mpkg which seems to be barely maintained and is hard to use. * Creates a single unified .pkg instead of a .mpkg. * The package we produce is in the modern, single-file format instead of a directory bundle that we have to zip up for download. In addition, this way of building the package now correctly: * Installs the manpages, bringing the `make osx`-generated package in line with the official Mac packages we publish on the website. * Installs files with the correct permissions instead of encoding the UID of the user who happened to build the package. Thanks to Augie for updating the test expectations.
-
Augie Fackler authored
-