Changes between Version 6 and Version 7 of PortingTips
- Timestamp:
- 05/01/08 01:05:52 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PortingTips
v6 v7 33 33 To automatically patch software with the BePorter tool, source tarballs should be diff'ed (cf. CreatePatch). 34 34 35 Most projects however use SCM/VCS software including CVS, Subversion, git and Mercurial and accept patches only against their latest (HEAD) development version. A possible strategy is:35 Most projects however use SCM/VCS software, including [wiki:dev-util/cvs CVS], [wiki:dev-util/subversion Subversion], [wiki:dev-util/git Git], [wiki:dev-util/mercurial Mercurial] and [wiki:dev-util/bzr Bazaar], and accept patches only against their latest (HEAD/trunk/master) development version. A possible strategy is: 36 36 37 37 1. Download and try the latest released source tarball. If it works, no further steps are necessary. 38 1. Otherwise, check if the project maintains a publicly accessible (anonymous) source code repository. You might be able to choose between a branch corresponding to the version number of the source tarball or trunk. (Terminology varies between the VCS tools.)38 1. Otherwise, check if the project maintains a publicly accessible (anonymous) source code repository. You might be able to choose between a branch corresponding to the version number of the source tarball, or trunk/master. (Terminology varies between the VCS tools.) 39 39 40 40 Doing so, you can easily track or revert your own changes, and this is the preferred format for submitting patches to the respective projects.
