-
-
Should be a blank line separating these. djblets is a third-party module, so it's in the second grouping of imports.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
The docs should first describe the function. Part of this description should contain the format that's being parsed, but that shouldn't be in the summary.
-
-
-
Would be nice to keep all this actual 'cm' execution code actually in the PlasticClient class and call out to it. Ideally, PlasticTool won't need to know anything about 'cm'.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Add Plastic SCM support
Review Request #1395 — Created Feb. 8, 2010 and submitted
Implemented support for the Plastic SCM server. http://www.codicesoftware.com Supports changesets, and branch diffs.
Tested (with post-review generating the diff file) against the latest version of Plastic SCM; also with post-review directly.
-
I've been unable to view this diff. It seems that the diff doesn't apply. Can you try uploading it again? I'd love to get this in for the upcoming beta.
DI
Review request changed
- Change Summary:
-
Uploaded diff again. This is the same as the previous diff, but hopefully it's viewable this time. Apologies for taking so long!
-
-
-
This should be: super(PlasticTool, self).__init__(repository) We don't do this everywhere yet, but we should start moving in that direction..
-
-
-
-
-
-
It is. It should probably be renamed at some point, though. PRE_CREATION really means "new files." So any referenced file being saved to the database that is actually a new, uncommitted file should be normalized to have this revision. The diff viewer will then use that to indicate if it's a new, uncommitted (upstream) file.
-
Out of curiosity, any plans to add some sort of indicators to the native diff output from the Plastic client?
-
-
-
-
-
-