- Aug 26, 2016
-
-
liscju authored
Import uses paths relative to the root of the repository, so when user imports patch with paths relative to the current working directory import aborts with 'unable to find file for patching'. This patch improves this situation by warning the user that paths are relative to the root of repository when patching fails.
-
- Sep 05, 2016
-
-
Hannes Oldenburg authored
-
- Aug 07, 2016
-
-
Yuya Nishihara authored
It was error-prone, and actually there was a typo, s/ancestorspec/ancestor/.
-
Yuya Nishihara authored
'negate' is mapped to 'string' at the above clause.
-
Yuya Nishihara authored
This should have caught the bug of 'keyvalue' operator fixed at 5004ef47f437. The catch-all pattern is useless since optimize() should be aware of all known operators.
-
- Sep 01, 2016
-
-
liscju authored
-
- Sep 02, 2016
-
-
liscju authored
-
- Aug 26, 2016
-
-
Yuya Nishihara authored
Since we have "bundled" flag, we no longer need to rephrase "ships-with-hg-core" to show as "internal".
-
- Aug 31, 2016
-
-
Yuya Nishihara authored
This is less magical than rephrasing ships-with-hg-core as internal, and we can distinguish "internal" liar. "tested with: internal" will be hidden by the next patch.
-
Yuya Nishihara authored
If testedwith were a string, ifcontains("3.2", testedwith) would match "3.2.1". New test added to cover that.
-
Pulkit Goyal authored
The int in Python 3 behaves as long so no need of L's in py3. Moreover we dont need long here.
-
- Aug 30, 2016
-
-
Martin von Zweigbergk authored
I always read the name "checkcase(path)" as "do we need to check for case folding at this path", but it's actually (I think) meant to be read "check if the file system cares about case at this path". I'm clearly not the only one confused by this as the dirstate has this property: def _checkcase(self): return not util.checkcase(self._join('.hg')) Maybe we should even inverse the function and call it fscasefolding() since that's what all callers care about?
-
Durham Goode authored
As part of refactoring the manifest, certain test cases started failing because writesubtrees was called with p1 and p2 manifests that had not been loaded (so accessing m1._dirs resulted in an empty set). Let's call _load on these before attempting to access _dirs. This was caught by tests when future patches were applied.
-
Augie Fackler authored
This was made more obvious by marmoute's recent rearrangement of this code.
-
Augie Fackler authored
If we don't do this, people without pygments installed in their Python 3 environment silently stop checking test-check-py3-compat, which isn't really what we wanted. This preserves stability of the test output while still letting anyone with a recent-enough Python 3 run the majority of the Python 3 compat checking test.
-
- Aug 26, 2016
-
-
Yuya Nishihara authored
The name "place" sounds odd. We can simply expose raw boolean values instead of switching external/internal literals.
-
Yuya Nishihara authored
"ships-with-hg-core" would be long enough to typo.
-
- Aug 30, 2016
-
-
Mark Ignacio authored
Improve the lock waiting warning message by explicitly saying that a host and process are holding the lock. This nudges confused new users in the direction of investigating the other process instead of removing the lock.
-
- Aug 28, 2016
-
-
Yuya Nishihara authored
And port "hg files" to test it. As you can see, extra indent is necessary to port to this API. I don't think we should switch every fm.formatter() call to "with" statement.
-
- Aug 26, 2016
-
-
Pierre-Yves David authored
Now that the one action that need different logic handle that using inheritance and overriding, we can remove that code.
-
Pierre-Yves David authored
All actions but one actually have the same constraints when it comes to validate the 'action.node' value. So we actually just add this code to a method that can be overwritten in the one action where it matters. The now unused 'contraints' related enum and class attribute will be cleaned up in the next changeset.
-
Pierre-Yves David authored
Action has a method dedicated to verifying its validity. So we move code related to constrains into that method. This requires a bit more context to the 'verify' method in the same fashion we were passing the 'prev' argument. This is an extra step before we can simplify the constraint handling code further.
-
Pierre-Yves David authored
It does not seem useful to convert to hex: it is an extra step and they are longer strings. So we stick to node for the logic. We only convert to short hex for error when needed. As a nice side effect this remove the explicit constant usage in'[12:]'. This will also help moving the code around later as we just have to access action.node.
-
Pierre-Yves David authored
An upcoming changeset will make the line where this variable is used slightly too long. Other later changesets will clean that up further and makes the variable unnecessary, so this is only temporary and it does seems useful to put anything more complicate in place.
-
Pierre-Yves David authored
We can just use 'action.node'.
-
Pierre-Yves David authored
There does not seem to be a reason for this to be a method. So we initialise the class attribute once and for all at creation time and drop the instance method.
-
Pierre-Yves David authored
That method is just returning self.node and is never overridden. We just use the attribute directly instead and get rid of the method. This is the beginning of series to simplify and unify verification of constraints for actions.
-
- Aug 29, 2016
-
-
Yuya Nishihara authored
Danek Duvall found that gpg-connect-agent of GnuPG 2.0 never starts gpg-agent daemon. The 2.1 way is documented as "gpg-coonect-agent /bye" [1], which appears to be different from the 2.0 way [2]. [1]: https://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPG_002dAGENT.html [2]: https://www.gnupg.org/documentation/manuals/gnupg-2.0/Invoking-GPG_002dAGENT.html Since "gpg-agent --daemon" of GnuPG 2.1 never prints environment variables, "eval $(gpg-agent --daemon)" would be valid only for GnuPG < 2.1, and we'll need a different workaround for 2.0. I have no 2.0 environment, I won't implement it.
-
- Aug 26, 2016
-
-
timeless authored
Before this, predecessor commits were being included in the count
-
- Aug 29, 2016
-
-
Maciej Fijalkowski authored
This file got dropped when the corresponding setup.py changes were made.
-
- Aug 24, 2016
-
-
Pierre-Yves David authored
The 'journal' naming is already used by the transaction journal. Having an unrelated group of file with such a close naming is confusing and error prone. We rename the file used by the 'journal' extension to use 'namejournal' as the extension track the location of various 'names'.
-
- Aug 25, 2016
-
-
timeless authored
-
timeless authored
demandimport and setuptools and decorator (from ironpython) and pygments leads to lots of fail. If demandimport is disabled we should skip testing it...
-
timeless authored
-
timeless authored
My bzr does not have bzrlib.revisionspec.RevisionSpec, and thus tests were failing because convert refused to believe in bzr, but hghave without this change thought it was available.
-
- Aug 23, 2016
-
-
Gregory Szorc authored
-
Gregory Szorc authored
There isn't a formal handshake protocol in the wire protocol. But clients almost certainly need to perform particular actions before they can communicate with a server optimally. So document what that is so people understand what's going on at connection establishment time.
-
Gregory Szorc authored
All capabilities from the history of the project are now documented.
-
Gregory Szorc authored
The HTTP and SSH transport protocols are documented. This includes how commands and arguments are serialized as well as response types.
-
Gregory Szorc authored
The Mercurial wire protocol is under-documented. This includes a lack of source docstrings and comments as well as pages on the official wiki. This patch adds the beginnings of "internals" documentation on the wire protocol. The documentation should have nearly complete coverage on the lower-level parts of the protocol, such as the different transport mechanims, how commands and arguments are sent, capabilities, and, of course, the commands themselves. As part of writing this documentation, I discovered a number of deficiencies in the protocol and bugs in the implementation. I've started sending patches for some of the issues. I hope to send a lot more. This patch starts with the scaffolding for a new internals page.
-