- Oct 15, 2014
- Oct 13, 2014
-
-
Angel Ezquerra authored
-
- Oct 15, 2014
-
-
Mads Kiilerich authored
Calling them args is not helpful.
-
- Oct 14, 2014
-
-
durin42 authored
-
- Oct 10, 2014
-
-
durin42 authored
Just makes it a little clearer what this method does.
-
- Oct 12, 2014
-
-
Pierre-Yves David authored
We do not have enough information to provide any finer data, but this is still useful information.
-
Pierre-Yves David authored
We do not have enough information to provide finer data, but this is still useful information.
-
- Oct 13, 2014
-
-
Pierre-Yves David authored
We also track execution of the changegroup hook. The important information here is to make sure the information that the transaction was processing a bundle2 is passed to hook. This will let most hooks disable themselves while waiting for the hook concluding bundle2 processing (the one we discovered to be not called for pull in the previous changesets).
-
Pierre-Yves David authored
We can notice that this transaction wide hook is only happening during push and it is missing changegroup-related information. We'll want to fix this but this is not what this patch is about.
-
- Oct 12, 2014
-
-
Pierre-Yves David authored
The push process uses a `stepsdone` attribute instead of a `todosteps` one (with the logic swapped). We unify the two process by picking the `stepsdone` version. I feel like `stepsdone` better fits extensions that would want to extend the push exchange process.
-
- Sep 27, 2014
-
-
Pierre-Yves David authored
We apply the same approach as for push and make the discovery extensible. There is only one user in core right now, but we already know we'll need something smarter for obsmarkers. In fact the evolve extension could use this to cleanly extend discovery. The main motivation for this change is consistency between push and pull.
-
- Oct 14, 2014
-
-
Yuya Nishihara authored
Otherwise, commandserver channel could be corrupted.
-
- Sep 03, 2014
-
-
Mike Edgar authored
This change allows a revision log to not fail integrity checks when applying a changegroup delta (eg from a bundle) results in a censored file tombstone. The tombstone is inserted as-is, so future integrity verification will observe the tombstone. Deltas based on the tombstone will also remain correct. The new code path is encountered for *exactly* the cases where _addrevision is importing a tombstone from a changegroup. When committing a file containing the "magic" tombstone text, the "text" parameter will be non-empty and the checkhash call is not executed (and when committing, the node will be computed to match the "magic" tombstone text).
-
- Oct 14, 2014
-
-
Mike Edgar authored
-
Mike Edgar authored
Two possible behaviors are defined for handling censored data: abort, and ignore. When we ignore censored data we return an empty file to callers requesting the file data.
-
- Oct 08, 2014
-
-
durin42 authored
This is another step closer to alternate manifest implementations that can offer different hashing algorithms.
-
durin42 authored
The rename is intended to provide a slight hint that it is manifest-specific.
-
durin42 authored
A future patch will introduce a new format, with a new class.
-
- Oct 03, 2014
-
-
Martin von Zweigbergk authored
-
- Oct 12, 2014
-
-
Martin von Zweigbergk authored
We do modify the lists that make up the status in several places, so it seems risky to use the same instance of a list for several different status types. Use a separate empty list for each type instead.
-
- Oct 03, 2014
-
-
Martin von Zweigbergk authored
In commands.summary(), we currently zip a list of labels with a list of statuses. This means the order of the status list has to match the list of the labels, which in turn means the status elements have to be inserted into specific places in the list. Let's instead group the labels and status data we want to display in a single list of pairs.
-
- Oct 05, 2014
-
-
Martin von Zweigbergk authored
By making checklocalchanges() return the full instance of the status class instead of just the first 4 elements of it, we can take advantage of the field names and not require the caller to remember the element indices.
-
Martin von Zweigbergk authored
-
Martin von Zweigbergk authored
-
- Oct 04, 2014
-
-
Martin von Zweigbergk authored
-
- Oct 03, 2014
-
-
Martin von Zweigbergk authored
It is safe to pass the full status to patch.diff() since it does its own slicing.
-
Martin von Zweigbergk authored
-
- Oct 04, 2014
-
-
Martin von Zweigbergk authored
-
- Oct 03, 2014
-
-
Martin von Zweigbergk authored
-
Martin von Zweigbergk authored
-
- Oct 05, 2014
-
-
Martin von Zweigbergk authored
This improves readability a bit by allowing us to refer to statuses by name rather than index.
-
- Oct 10, 2014
-
-
Martin von Zweigbergk authored
The various status types are currently documented on the dirstate.status() method. Now that we have a class for the status types, it makese sense to document the status types there instead. Only leave the bits related to lookup/unsure in the status() method documentation.
-
- Oct 14, 2014
-
-
Martin von Zweigbergk authored
-
- Oct 10, 2014
-
-
Martin von Zweigbergk authored
Callers of various status() methods (on dirstate, context, repo) get a tuple of 7 elements, where each element is a list of files. This results in lots of uses of indexes where names would be much more readable. For example, "status.ignored" seems clearer than "status[4]" [1]. So, let's introduce a simple named tuple containing the 7 status fields: modified, added, removed, deleted, unknown, ignored, clean. This patch introduces the class and updates the status methods to return instances of it. Later patches will update the callers. [1] Did you even notice that it should have been "status[5]"? (tweaked by mpm to introduce the class in scmutil and only change one user)
-
- Oct 04, 2014
-
-
Martin von Zweigbergk authored
In lfdirstatestatus(), the status tuple gets deconstructed, the lists get updated, and then an identical status tuple gets created and returned. Change it so we simply return the original tuple.
-
Martin von Zweigbergk authored
The status tuple returned from dirstate.status() has an additional field compared to the other status tuples: lookup/unsure. This field is just an optimization and not something most callers care about (they want the resolved value of 'modified' or 'clean'). To prepare for a single future status type, let's separate out the 'lookup' field from the rest by having dirstate.status() return a pair: (lookup, status).
-
- Oct 13, 2014
-
-
Martin von Zweigbergk authored
Now that we have a separate variable for the original 'm1' manifest, we can safely update the nodeid of the file in the new manifest in the same place as we update the flags.
-
Martin von Zweigbergk authored
In localrepo.commitctx(), p1's manifest is copied and used as the basis for the manifest that is about to be committed. The way the copy is updated makes it safe to use it where the original p1's manifest is wanted. For readability, though, a separate variable for each purpose would be clearer. Make it so.
-
Martin von Zweigbergk authored
The 'lock' variable is initialized to None, but before it's ever read, it's assigned again.
-