Closed (fixed)
Project:
Drupal PM (Project Management)
Version:
7.x-2.x-dev
Component:
Code
Priority:
Minor
Category:
Task
Assigned:
Reporter:
Created:
11 Mar 2014 at 14:03 UTC
Updated:
11 Jan 2015 at 12:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
juliangb commentedTwo initial patches covering specific parts of the codebase.
I have tried to focus on areas that are unlikely to cause merge conflicts.
Neither patch should affect module functionality at all.
Comment #2
juliangb commentedTwo patches from #1 committed to 7.x-1.x.
Comment #8
dbt102 commentedCan I help w/ this cleanup? Thinking I'd just grab a file and do what I can, then post it up as a patch?
Comment #9
d34dman commentedThat would be a great way to get started with development part of this project. But please note that we are now working on 7.x-2.x part of the project. And let us know which part you are working on so we don't duplicate our efforts.
Comment #10
juliangb commentedGood point - these changes should be made on the 2.x branch.
Also, when looking at http://pareview.sh/pareview/httpgitdrupalorgprojectpmgit-7x-2x, I suggest selecting the "repeat review" option after each commit so that all the warnings / errors are shown correct and associated with the correct line numbers.
Comment #11
dbt102 commentedOk, will start with README.txt to get started on a workflow.
Comment #12
dbt102 commentedComment #14
dbt102 commentedHmmm... something doesn't look right...
http://pareview.sh/pareview/httpgitdrupalorgprojectpmgit-7x-1x reports
http://pareview.sh/pareview/httpgitdrupalorgprojectpmgit-7x-2x reports
Did the changes get applied to pm_7x_1x somehow? I'll submit readme_2x patch in a minute. No big deal, just want to make sure I understand my workflow well as I get started.
Comment #15
dbt102 commentedComment #17
juliangb commentedFor some reason the patch isn't applying properly to 1.x, but the 2.x one did and I've committed it. Thanks!
Comment #30
juliangb commentedI think we've got this done as much as is necessary.