- Aug 26, 2016
-
-
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.
-
- Aug 18, 2016
-
-
Yuya Nishihara authored
Several fields are renamed to be consistent with the annotate command, which doesn't mean the last call for the name unification [1]. Actually, I'd rather rename line_number to linenumber, linenum, lineno or line, but I want to port the grep command to formatter first. [1]: https://www.mercurial-scm.org/wiki/GenericTemplatingPlan#Dictionary I don't have any better name for the list of matched/unmatched texts, so they are just called as "texts".
-
Yuya Nishihara authored
These columns should always be available in JSON or template outputs. The "change" column is excluded because it has no useful data unless --all is specified.
-
Yuya Nishihara authored
Prepares for formatter support. We need field names without "grep.".
-
Yuya Nishihara authored
Prepares for formatter support.
-
Yuya Nishihara authored
As preparation for formatter support, this and the next patch split linestate.__iter__() into two functions, line scanner and displayer. New code uses regexp.search(str, pos) in place of regexp.search(substr), which appears to fix a bug of highlighting.
-
- Jul 05, 2016
-
-
liscju authored
Documentation gave the usage pattern as '[OPTION]... [PATTERN]...' when the command match given files as relpaths by default.
-
- Aug 25, 2016
-
-
Matt Mackall authored
This does a fall-back check for style files or directories that are in Mercurial's template path for user convenience. We intentionally don't use this for the built-in coal style because we don't want the style to mysteriously break if the working directory just happens to have a file named "paper".
-
- Aug 23, 2016
-
-
Augie Fackler authored
This should be extremely useful for helping users debug without having to see their complete configuration. Shell aliases do not get their expansion logged, because we don't look and see if we're in a repo before we dive into the execution of a shell alias. As a result, the ui object doesn't know where to log.
-
- Aug 25, 2016
-
-
Augie Fackler authored
This is what happens if you run the test in a FreeBSD Jail, rather than "connection refused".
-
Augie Fackler authored
This fixes the test on FreeBSD, where the stock unzip doesn't understand symlinks.
-
Augie Fackler authored
unzip(1) from the FreeBSD base system does not understand symlinks, so test-archive-symlinks is busted.
-
Augie Fackler authored
These make test failures scarier than they are.
-
- Aug 23, 2016
-
-
Augie Fackler authored
I've caught multiple extensions in the wild lying about being 'internal', so it's time to move the goalposts on people. Goalpost moving will continue until third party extensions stop trying to defeat the system.
-
- Aug 25, 2016
-
-
Yuya Nishihara authored
The license message isn't exported, which I don't think is useful and I couldn't find a way to restructure it for JSON or template outputs.
-
- Aug 16, 2016
-
-
Yuya Nishihara authored
Prepares for formatter support, where translation should be disabled conditionally.
-
Yuya Nishihara authored
This patch just moves "if ui.verbose:" to the inner loop, as preparation for formatter support.
-
- Mar 13, 2016
-
-
Yuya Nishihara authored
We sometimes need to build nested items by formatter, but there was no convenient way other than building and putting them manually by fm.data(): exts = [] for n, v in extensions: fm.plain('%s %s\n' % (n, v)) exts.append({'name': n, 'ver': v}) fm.data(extensions=exts) This should work for simple cases, but doing this would make it harder to change the underlying data type for better templating support. So this patch provides fm.nested(field), which returns new nested formatter (or self if items aren't structured and just written to ui.) A nested formatter stores items which will later be rendered by the parent formatter. fn = fm.nested('extensions') for n, v in extensions: fn.startitem() fn.write('name ver', '%s %s\n', n, v) fn.end() Nested items are directly exported to a template for now: {extensions % "{name} {ver}\n"} There's no {extensions} nor {join(extensions, sep)} yet. I have a plan for them by extending fm.nested() API, but I want to revisit it after trying out this API in the real world.
-
- Aug 15, 2016
-
-
Yuya Nishihara authored
New converter classes will be reused by a nested formatter. See the next patch for details. This change is also good in that the default values are defined uniquely by the baseformatter.
-
- Aug 24, 2016
-
-
Jun Wu authored
Previously, the SIGWINCH handler does not get cleared and if the commit message editor also needs SIGWINCH handling (like vim), the two SIGWINCH handlers (the editor's, ours) will have a race. And we may erase the editor's screen content. This patch restores SIGWINCH handler to address the above issue.
-
- Aug 20, 2016
-
-
Maciej Fijalkowski authored
-
- Jul 28, 2016
-
-
Maciej Fijalkowski authored
-
- Aug 19, 2016
-
-
Tony Tung authored
There's no reason to leave the file behind.
-
- Aug 24, 2016
-
-
Siddharth Agarwal authored
See the comment for a detailed explanation why. Even though this is a bug, I've sent it to 'default' rather than 'stable' because it isn't triggered in any code paths in stock Mercurial, just with the merge driver included. For the same reason I haven't included any tests here -- the merge driver is getting a new test.
-