- Jan 16, 2015
-
-
Eric Sumner authored
This will also be used for 'hg unbundle'
-
durin42 authored
This will help us not regress this case in the future.
-
- Jan 15, 2015
-
-
Eric Sumner authored
This enables debugbundle to print supporting info for bundle2 files.
-
- Jan 13, 2015
-
-
Matt Harbison authored
This was a remnant of the code prior to overridding cmdutil.add().
-
Matt Harbison authored
The --large, --normal and --lfsize args couldn't be passed to a subrepo before, and files in the subrepos would be added silently (if -v wasn't specified) as normal files. As an added bonus, 'hg add --dry-run' no longer prints that largefiles would also be added as normal files as well.
-
Matt Harbison authored
The largefiles extensions needs to be able to pass --large, --normal and --lfsize to subrepos via cmdutil.add() and hgsubrepo.add(). Rather than add additional special purpose arguments, stop extracting the existing args from the **opts passed to commands.add() and just pass them along.
-
- Dec 31, 2014
-
-
Matt Harbison authored
The arguments will need to stay present when making add work with subrepos.
-
- Jan 11, 2015
-
-
Angel Ezquerra authored
cd79fb4d75fd introduced a way to share bookmarks. When a repository share that shares bookmarks was created, a .hg/bookmarks.shared file was created to mark the repository share as one that shares its bookmarks. We have plans to introduce other levels of sharing, including a "full share" mode. Rather than creating a new ".shared" file for each new thing that we may want to share It seems better to create a single "shared" file that will list what is shared for a given shared repository. This should make it much easier to get a list of everything that is shared by a given shared repository. The shared file contains a list of shared "items" (such as bookmarks). Each shared "item" is added as a new line in the file. For now the only possible entry in the file is "bookmarks".
-
- Nov 02, 2014
-
-
Mads Kiilerich authored
-
- Jan 16, 2015
-
-
Mads Kiilerich authored
Use the new and more TLS support in Python 2.7.9.
-
Mads Kiilerich authored
We should utilize (and test) the big API changes and new TLS functionality in Python 2.7.9 whenever possible.
-
- Jan 11, 2015
-
-
Angel Ezquerra authored
This change touches every module in which repository.wopener was being used, and changes it for the equivalent repository.wvfs. It should now be possible to remove localrepo.wopener.
-
- Jan 10, 2015
-
-
Angel Ezquerra authored
This change touches every module in which repository.sopener was being used, and changes it for the equivalent repository.svfs. It should now be possible to remove localrepo.sopener.
-
- Jan 15, 2015
-
-
Angel Ezquerra authored
This change touches every module in which repository.opener was being used, and changes it for the equivalent repository.vfs. This is meant to make it easier to split the repository.vfs into several separate vfs. It should now be possible to remove localrepo.opener.
-
Sean Farley authored
Now that we have the machinary to change the log name and the color label used, let's use that. Tests have been updated accordingly.
-
Sean Farley authored
Previously, there was no way to change the color label used for 'hg log' output. This patch just adds the member to the object, a future patch will change 'hg log' to use this.
-
Sean Farley authored
Previously, there was no way to change the name used for 'hg log' output. This was inconvenient for extensions that want a template name longer than 12 characters (e.g. remotebookmarks) but a different name for 'hg log'. This patch only adds the member to the object, a future patch will update the 'hg log' code.
-
Sean Farley authored
This is just a style change but makes adding new arguments more robust for callers.
-
Sean Farley authored
None of the arguments are truly optional but this makes adding future arguments more robust and perhaps optional.
-
- Jan 16, 2015
-
-
Gregory Szorc authored
Extensions can declare compatibility with Mercurial versions. If an error occurs, Mercurial will attempt to pin blame on an extension that isn't marked as compatible. While all bets are off when it comes to the internal API, my experience has shown that a monthly/patch release of Mercurial has never broken any of the extensions I've written. I think that expecting extensions to declare compatibility with every patch release of Mercurial is asking a bit much and adds little to no value. This patch changes the blame logic from exact version matching to only match on the major and minor Mercurial versions. This means that extensions only need to mark themselves as compatible with the major, quarterly releases and not the monthly ones in order to stay current and avoid what is almost certainly unfair blame. This will mean less work for extension authors and almost certainly fewer false positives in the blame attribution.
-
Gregory Szorc authored
Mercurial doesn't define the 3rd "patch" version field for major releases. Don't use it in tests.
-
Gregory Szorc authored
There was a mountain of text in this file that made reading the tests difficult. Inserting some line breaks greatly improves the situation.
-
- Dec 19, 2014
-
-
Pierre-Yves David authored
The binary format description has always stated that the parttype should be simple, but it was never really enforced. Recent discussions have convinced me we want to keep the part type simple and easy to debug. There is enough extensibility in the rest of the format.
-
- Jan 15, 2015
-
-
Matt Harbison authored
I still get the following diff on Windows 7 with NTFS. I'm not sure if it is expected and we should wildcard the link count, or if something needs to be fixed. @@ -58,7 +58,7 @@ $ ln bar baz $ f bar -n baz -l --hexdump -t --sha1 --lines=9 -B 20 - bar: file, links=2, newer than baz, sha1=612ca68d0305c821750a + bar: file, links=0, newer than baz, sha1=612ca68d0305c821750a\r (esc) 0000: 31 0a 32 0a 33 0a 34 0a 35 0a 36 0a 37 0a 38 0a |1.2.3.4.5.6.7.8.| 0010: 39 0a |9.|
-
- Jan 14, 2015
-
-
Mads Kiilerich authored
Sleep can only travel forward in time, not back.
-
- Jan 15, 2015
-
-
Pierre-Yves David authored
When the manifest revision is stored as a delta against a non-parent revision, '_adjustlinkrev' could miss some file update because it was using the delta only. We now use the 'fastread' method that uses the delta only when it makes sense. A test showcasing on the of possible issue have been added.
-
Matt Mackall authored
-
- Jan 14, 2015
-
-
Mads Kiilerich authored
self._rbcrevslen is used to keep track of the number of good records on disk. It should thus not be updated before the records actually have been written to disk.
-
Mads Kiilerich authored
The cache files are usually append only but will automatically be truncated and recover in exceptional situations. Add a debug notice when such exceptional situations are encountered.
-
Mads Kiilerich authored
The tests that were added with the revision branch cache in 678f53865c68 had suffered from bit rot in the development iterations. They were no longer that "good". Now, the tests are rewritten and reworked to be more readable and maintainable and relevant for the actual implementation. This also utilizes the new 'f' helper tool for keeping an eye the cache files.
-
Mads Kiilerich authored
This tool is like the collection of tools found in a unix environment but are cross platform and stable and suitable for our needs in the test suite. The main reason it is "needed" now is for hexdump of revision branch cache to keep an eye on how it changes and make sure the format is stable. It is a very generic tool that can end up being used a lot in tests, so I gave it very generic name.
-
Mads Kiilerich authored
The testdir is already added to $PYTHONPATH - I think it makes sense and is convenient to add it to $PATH too. The following binaries are invoked from tests using full path with $TESTDIR/ - they can now be used without specifying path: dumbhttp.py dummyssh filterpyflakes.py generate-working-copy-states.py get-with-headers.py hghave histedit-helpers.sh killdaemons.py md5sum.py notcapable printenv.py readlink.py revlog-formatv0.py run-tests.py svn-safe-append.py svnxml.py tinyproxy.py
-
- Jan 12, 2015
-
-
Mike Edgar authored
-
Mike Edgar authored
When receiving a delta via exchange, three possible storage outcomes emerge: 1. The delta is added directly to the revlog. ("fast-path") 2. A freshly-computed delta with a different base is stored. 3. The new revision's fulltext is computed and stored outright. Both (2) and (3) require materializing the full text of the new revision by applying the delta to its base. This is typically followed by a hash check. The new flags argument allows callers to _addrevision to signal that they expect that hash check to fail. We can use this opportunity to verify that expectation. If the hash fails, require the flag be set; if the hash passes, require the flag be unset. Rather than simply eliding the hash check, this approach provides some assurance that the censored flag is not applied to valid revisions. Read more at: http://mercurial.selenic.com/wiki/CensorPlan
-
Mike Edgar authored
For revlog index flags to be useful to other parts of Mercurial, they need to be settable when writing revisions. The current use case for revlog index flags is the censorship feature: http://mercurial.selenic.com/wiki/CensorPlan While the censor flag could be inferred in _addrevision by interrogating the text/delta being added, that would bury the censorship logic and inappropriately couple it to all revision creation.
-
Mike Edgar authored
This flag bit will be used to cheaply signal censorship presence to upper layers (exchange, verify). It indicates that censorship metadata is present but does not attest to the verifiability of that metadata. For the censorship design, see: http://mercurial.selenic.com/wiki/CensorPlan
-
- Jan 11, 2015
-
-
Angel Ezquerra authored
It has been replaced with localrepo.wvfs.
-
- Jan 10, 2015
-
-
Angel Ezquerra authored
It has been replaced with localrepo.svfs.
-
Angel Ezquerra authored
It has been replaced with localrepo.vfs. In the future we may split the vfs into different vfs objects to access different elements of the repository.
-
- Jan 14, 2015
-
-
Augie Fackler authored
Nobody outside sslutil should be using these constants anyway.
-