- Oct 14, 2015
-
-
Siddharth Agarwal authored
This will be useful to other calling code that would be interested in what the individual hooks return.
-
Siddharth Agarwal authored
This will allow other code to run a predetermined series of hooks.
-
- Mar 10, 2015
-
-
kiilerix authored
Avoid the pointless numeric rev.diff patch names. Instead, do like mbox extension does and create meaningful patch names.
-
- Oct 15, 2015
-
-
Mads Kiilerich authored
-
Mads Kiilerich authored
-
- Oct 16, 2015
-
-
Mads Kiilerich authored
-
- Oct 15, 2015
-
-
Gregory Szorc authored
We don't appear to print error codes elsewhere. The error codes are inconsistent between at least Linux and OS X and are more trouble than they are worth. Humans care about the error string more than the code anyway. A glob was also added to pave over differences in error strings between Linux and OS X.
-
- Oct 14, 2015
-
-
Augie Fackler authored
-
Augie Fackler authored
Very often in my life I'm finding that the only configured merge tool present on the system is vimdiff[0], and it's currently impossible (as far as I can tell) short of specifying `ui.merge = `[1] to actually *disable* a merge tool. This allows vimdiff-haters to put: [merge-tools] vimdiff.disable = yes in their ~/.hgrc and never see vimdiff again. I'm stopping short of putting this as a commented out entry in the sample new user hgrc (seen when a user runs `hg config --edit` with no ~/.hgrc) for now, but I might come back and do that later. 0: vimdiff is at an awkward intersection: it's usually installed by the vim package which is often installed as a vi substitute, so it's mere presence doesn't imply me wanting it, unlike (say) kdiff3. 1: There's a related problem I ran into today where specifying `ui.merge = :merge` failed because :merge isn't a command, which I think is a regression. I'll try and figure that out and at least file a bug.
-
Sean Farley authored
-
- Oct 15, 2015
-
-
Pierre-Yves David authored
One of the main goal of having consolidated destination function is to allow extension to play with this logic. We extract sub logic to make is wrapping more practical.
-
Pierre-Yves David authored
One of the main goal of having consolidated destination function is to allow extension to play with this logic. We extract sub logic to make is wrapping more practical.
-
Pierre-Yves David authored
We want extension to be able to easily override or add new way to select the default update destination. We use the same list + dict approach as in other parts of the code.
-
Pierre-Yves David authored
One of the main goal of having consolidated destination function is to allow extension to play with this logic. We extract sub logic to make is wrapping more practical.
-
Pierre-Yves David authored
One of the main goal of having consolidated destination function is to allow extension to play with this logic. We extract sub logic to make is wrapping more practical.
-
Pierre-Yves David authored
One of the main goal of having consolidated destination function is to allow extension to play with this logic. We extract sub logic to make is wrapping more practical.
-
Pierre-Yves David authored
This block was overwriting any result from the previous block anyway. So we move it first to prove it is possible and we'll extract it in its own function in the next patch.
-
Pierre-Yves David authored
We'll move the obsolete related logic first (as it is overwriting any other anyway) to make the next patch clearer we add indentation in this one.
-
Pierre-Yves David authored
One of the main goal of having consolidated destination function is to allow extension to play with this logic. We extract sub logic to make is wrapping more practical.
-
Pierre-Yves David authored
We make the name consistent with the other similar revsets and make sure it has minimal tests.
-
Pierre-Yves David authored
There is little value in using the revset instead of the function.
-
Pierre-Yves David authored
This makes it much simple to wrap for other extension.
-
Pierre-Yves David authored
We make the name consistent with the one used by '_destupdate' and we ensure the code is run by testing it (abort is expected and merge would).
-
Pierre-Yves David authored
There is no real value in using the revset over the function. The revset have no remaining users and will be taken care of in a later changesets.
-
Pierre-Yves David authored
Function in destutil are much simpler to wrap and more flexible than revset. This also help consistency as 'destupdate' live here and cannot become a pure revset anyway.
-
Pierre-Yves David authored
The revset is not ready for prime time yet. However it is useful to have some version of it exposed to help candidate users to play with it and provide feedback on what we should aim at. We add a small test to make sure the code runs.
-
- Oct 14, 2015
-
-
Augie Fackler authored
The upcoming cg3 will need different logic for unpacking manifests.
-
- Oct 01, 2015
-
-
Augie Fackler authored
A future change will introduce a new function on a cg3packer that can pack treemanifests as well as flatmanifests.
-
- Sep 30, 2015
-
-
Augie Fackler authored
Since I'm spending the time to understand this code, I may as well leave it clearer than I found it.
-
- Sep 29, 2015
-
-
Augie Fackler authored
I'm about to add a cg3, and it seems prudent to annotate what formats support what features. It strikes me that we may want to consider moving to a more feature-oriented model in the future, but we'll see how that looks in a little while I guess.
-
- Oct 14, 2015
-
-
Augie Fackler authored
This should help future readers at least a little.
-
Augie Fackler authored
-
Augie Fackler authored
I'm not sure what to do abstraction-wise here. It might be more sensible to make a memoryrepo that could apply a bundle in-memory and then we could make the changegroup data be strictly an applyable stream, but that's an idea for Later.
-
Augie Fackler authored
The new convention is that bundles contain changegroups. bundle1 happens to *only* be a changegroup, but bundle2 is a more featureful container that isn't something you can pass to addgroup().
-
- Oct 13, 2015
-
-
Augie Fackler authored
I'm trying to reason about the public surface area of this module now, so it's worth tagging private things as such.
-
Augie Fackler authored
-
Augie Fackler authored
This is in localpeer, so it lives. Had it been in localrepo instead, I would have tried to exterminate it.
-
Augie Fackler authored
-
Augie Fackler authored
-
Augie Fackler authored
-