Submitted by rfay on
Git is so smart about merging that it's often possible to referesh a stale patch in the queue using just git, without even looking at the contents of the patch. (I'm not saying you shouldn't look at any patch you post, just that git will often do all the refeesh work for you.)
- Update to the latest version of the project you're working with.
- Use git log to find the hash of a commit near or just before the time the patch was posted.
- Create a branch from that commit:
git checkout -b <date_based_branch_name> <commit_hash>. (I often use the date for the branch name:
git checkout -b aug10 <hash>
- Apply the patch. It should apply cleanly unless there was already something wrong with it when it was created.
git statusto make sure that all your changes are staged, then commit the results.
- Create a new branch for the updated patch. I'll use
git checkout -b bundles_removed_1245332_04 origin/8.x, which branches off of 8.x just for this feature branch.
- Merge the date-based branch:
git merge <date_branch>
- If all goes well, you have a clean merge, and you can create a patch. In this case,
git diff origin/8.x >drupal.bundle_warning_1245332_04.patch
- If you still have a merge conflict, you probably only have the really relevant part of the conflict (changes actually made in your patch which conflict with changes which have been committed since the issue was last active.) In that case, you can use
git mergetoolto reconcile the differences, but that's for another session.
For just updating a patch that was obsoleted by the D8 core files move patch in November, see xjm's excellent, focused article.
Here's the screencast:
Submitted by Janez Urevc on
Thank you for that info. It is VERY usefull!