You could scan /sites/all/modules for *.diff files to produce a list of patches that are distributed with modules. You could optionally filter the list on only enabled modules. However, some modules may require a patch to be installed before they can be enabled.

Comments

aidanlis’s picture

aidanlis commented
Title: List patches distribulted with modules » Allow importing of patches from the filesystem

I've committed a basic discovery mechanism to VCS which lists the patches found but doesn't allow you to do anything with them.

I'm not sure how this functionality should tie in to the rest of the module, I guess being able to highlight patches and [x] import them would be the next step.

DrewMathers’s picture

DrewMathers commented

The next thing would be the ability to apply these patches.

aidanlis’s picture

aidanlis commented
Status: Active » Postponed

a) For discovered patches, we need an "import" and "apply" button which would create a node and set the details. We also need a mechanism to ignore patches that are already added.

b) For registered patches, we should import them automatically.

Everything is in place, but I don't have time to implement this.

DrewMathers’s picture

DrewMathers commented

For discovered patches, we need an "import" and "apply" button which would create a node and set the details.

Could a VBO create node action do this?

We also need a mechanism to ignore patches that are already added.

Not necessarily. Users still might want an option to revert these patches. However, you could use this: #1133614: Display patch status