Git diff trunk 30000-add-more-alots > 30000.x.Superglobals $GLOBALS $_SERVER $_REQUEST $_POST $_GET PHP RegEx Here is an example sequence of commands to update your trunk branch then refresh your patch on top of the latest code (make sure you have no uncommitted changes in your repository first): This is a great way to keep your patches up to date, and it’s much easier with Git than with svn. † If your trunk branch has changed since you last worked on your patch (for example, if you’ve pulled down the latest code), you’ll need to rebase your branch against the latest code. When downloading the repository from git, a few of the PHPUnit tests related to the importer plugin will fail because the tests/phpunit/data/plugins/wordpress-importer directory is not contained in the git repositories. This makes it many times easier for committers to review and commit your changes. We strongly recommend running the PHPUnit test suite (and writing unit tests for your patch) before submitting it to Trac. Upload the patch to the appropriate Trac ticket.Example command: $ git diff trunk 30000-add-more-alots > 30000.diff if there are already patches on the ticket). In general, the file name should be the ticket number you are working on with. Once you’re ready to submit your patch to Trac, generate a patch file using git diff, specifying that the output should be saved in a.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |