- Douglas Gottlieb, Vice President, Creative Group at Barnes&Noble.com
- Kevin Meyers, Meyers Design Inc.
- Robert Douglas, Senior Drupal Advisor, Acquia
We recently started on a project and began work implementing the features when we were told that it needed to be based on Pressflow. After a small moment of panic at the thought of having to redo all of the work done thus far, Dave assured me that it was a simple drop-in to replace regular 'vanilla' Drupal core with Pressflow. Still, leaving nothing to chance, I wanted to see just what these differences were and how it would effect my current code base. Was it really that simple?
So I downloaded Pressflow and came up with a diff file between my current code base for my project and Pressflow so that I could see first-hand all of the changes that would be made. It was a little trickier than a simple diff command, as there are some .bzr files within the Pressflow installation, .git file in both, and CVS file in my own. Plus I already have a bunch of modules within my current code base that I did not want reflected within my diff file. The goal was to come up with a succinct patch that could be applied to any Drupal core in order to change it into Pressflow.
Here is the command I came up with to accomplish this:
diff -uNpr -x .git -x CVS -x .gitignore -x all [my code base location] [pressflow code base location]
The resulting patch file is attached.
| Attachment | Size |
|---|---|
| pressflow-6.patch | 378.94 KB |
// comments
Which version of drupal did
Which version of drupal did you create this diff from? 6.15?
Yes, this was against 6.15
Yes, this was against 6.15
// add comment