- May 17, 2014
-
-
Steven Brown authored
The check-code tool now expects the "desc" keyword to be followed by the "websub" filter, with the following exceptions: a) It has no filters at all, e.g. a changeset description in the raw style templates or the repository description in the summary page. b) It is followed by the "firstline" filter, e.g. the first line of the changeset description is displayed as a summary or title.
-
Steven Brown authored
For example, this is useful for linking from the feed reader to a bug tracker. This follows the existing pattern used within the hgweb templates. With the exception of the raw style, all usages of the changeset "desc" keyword are now followed by either the "firstline" filter or the "websub" filter. When "websub" is used, it always follows the "escape" filter.
-
Steven Brown authored
To improve the readability.
-
Steven Brown authored
This matches the existing tests for the atom feeds.
-
- Apr 23, 2014
-
-
Sean Farley authored
Now that we have the machinery in place, we call the context method for changing the match object in the case of comparing the working directory with its parent. This removes the last of the hard-coded workingctx knowledge in localrepo paving the way for us to remove localrepo.status completely.
-
- Apr 24, 2014
-
-
Sean Farley authored
This patch encapsulate the logic for changing the match.bad function when comparing against the working directory's parent. Future patches will remove more of the 'if ... else' blocks in localrepo.status that test for this working directory parent case.
-
- Apr 23, 2014
-
-
Sean Farley authored
This patch paves the way to allow a workingctx to override the match object with a custom 'bad' method for cases where status is sent a directory pattern.
-
- Apr 24, 2014
-
-
Sean Farley authored
This patch maintains the fast path for workingctx which is to not build a manifest if the working directory is being compared to its parent since, in this case, we can just copy the parent manifest.
-
- Apr 23, 2014
-
-
Sean Farley authored
This unpacking is unneeded now because previous patches have removed the need for this method to modify each of these variables in favor of passing the whole set around to pre/post hook methods of the corresponding context object.
-
- Apr 22, 2014
-
-
Sean Farley authored
-
Sean Farley authored
With this patch, we are one step closer to removing 'if ... else' logic in localrepo.status for testing if the context is the working directory or not. Future patches will replace those blocks of code with a call to the context's _poststatus hook so that each context object will do the right thing depending on the situation.
-
Sean Farley authored
This patch adds a private _poststatus method so that certain contexts, such as workingctx, can add custom post-processing to status.
-
Sean Farley authored
-
Sean Farley authored
With this patch, we are one step closer to removing 'if ... else' logic in localrepo.status for testing if the context is the working directory or not. Future patches will replace those blocks of code with a call to the context's _prestatus hook so that each context object will do the right thing depending on the situation.
-
Sean Farley authored
This patch adds a private _prestatus method so that certain contexts, such as workingctx, can add custom pre-processing to status.
-
Sean Farley authored
-
Sean Farley authored
This method is a copy of localstatus.status's core logic. Later patches will clean up some of the dense coditionals in the for loop.
-
Sean Farley authored
-
Sean Farley authored
This movement is a small step in getting rid of the 'if ... else' logic for testing the current working directory with its parent. Previously, the deleted, unknown, and ignored variables were set in a combination of before an 'if ... else' block and within the block. This moves the variables to be set outside the loop in one common place.
-
- Apr 15, 2014
-
-
Sean Farley authored
-
- Mar 11, 2014
-
-
Sean Farley authored
-
- Apr 24, 2014
-
-
Sean Farley authored
This method is a duplicate of localrepo.mfmatches and sets the stage for factoring localrepo.status into a context method that will be customizable based on inheritance and object type.
-
- Mar 11, 2014
-
-
Sean Farley authored
This is a small patch to help streamline keeping tracking of the list of files for status in a variable already called 'r' ('s' is for subrepos in this method). We now move the setting of it out of an 'if' block so that we can later refactor more code into the context objects.
-
- Apr 20, 2014
-
-
Gregory Szorc authored
Now that unittest mode is functionally equivalent to the default mode, we switch the default execution mode to unittest and remove the choice of different execution modes.
-
- Apr 22, 2014
-
-
Gregory Szorc authored
unittest sometimes does a str(test) and the default implementation doesn't do the right thing. So we override it.
-
- Apr 21, 2014
-
-
Gregory Szorc authored
Unlike unittest's defaults, our result formatter does not print stack traces. Here, we change TestResult.addFailure() to be compatible with the existing/default execution mode.
-
- Apr 20, 2014
-
-
Gregory Szorc authored
rmtree() may fail under certain conditions. We ignore failures at the individual test level because they can interfere with test execution. Furthermore, we'll reattempt deletion in the high-level test runner after all tests have finished. Note that this patch is not a code refactor like most of the patches before it. This change logically makes sense given the execution behavior of the tests.
-
Gregory Szorc authored
There is an execution mode on run-tests.py that stops after the first failure. unittest mode was previously not obeying this option. This patch fixes that.
-
Gregory Szorc authored
Our unittest TextTestRunner now prints output similar to the output from the default execution mode - the output people expect from run-tests.py.
-
Gregory Szorc authored
A subsequent patch will have unittest print tests for us. Don't perform old-style printing when in unittest mode.
-
Gregory Szorc authored
-
Gregory Szorc authored
-
- Apr 21, 2014
-
-
Gregory Szorc authored
-
- Apr 20, 2014
-
-
Gregory Szorc authored
testtmp is now a member variable of our test class. It's value is computed during instance creation and the directory is managed via the lifetime of the test object.
-
Gregory Szorc authored
As code is being moved between functions, we need a member variable to hold skipped state.
-
Gregory Szorc authored
-
Gregory Szorc authored
Subsequent patches move post-test actions into tearDown(). This requires tearDown() to have access to the last result.
-
Gregory Szorc authored
-
Gregory Szorc authored
A subsequent patch that will introduce tearDown() requires test execution state be stored in the instance.
-
Gregory Szorc authored
This brings run() more compatible with unittest.TestCase.run()
-