|
| 1 | +commit-patch |
| 2 | +============ |
| 3 | + |
| 4 | +Commit patches to Darcs, Git, Mercurial, Bazaar, Monotone, Subversion, or CVS |
| 5 | + |
| 6 | + |
| 7 | +Prerequisites |
| 8 | +------------- |
| 9 | + |
| 10 | +commit-patch relies on several programs to get the job done: |
| 11 | + |
| 12 | +- [perl](http://www.perl.org) |
| 13 | +- [patch](http://www.gnu.org/software/patch/) |
| 14 | +- [interdiff](http://cyberelk.net/tim/software/patchutils/) |
| 15 | +- cp - Ideally installed on your system already. :-) |
| 16 | + |
| 17 | +and, of course, one of: |
| 18 | + |
| 19 | +- [darcs](http://darcs.net/) |
| 20 | +- [git](http://git.or.cz/) |
| 21 | +- [mercurial](http://www.selenic.com/mercurial/) |
| 22 | +- [bazaar](http://bazaar-vcs.org/) |
| 23 | +- [monotone](http://www.monotone.ca/) |
| 24 | +- [subversion](http://subversion.tigris.org/) |
| 25 | +- [cvs](http://www.nongnu.org/cvs/) |
| 26 | + |
| 27 | +## Installing Prerequisites |
| 28 | + |
| 29 | +On Debian/Ubuntu: |
| 30 | + |
| 31 | + apt-get install libipc-run-perl patch patchutils |
| 32 | + |
| 33 | +On Fedora: |
| 34 | + |
| 35 | + yum install perl-IPC-Run patch patchutils |
| 36 | + |
| 37 | +On Mac OS X w/ Homebrew <http://mxcl.github.io/homebrew/> |
| 38 | + |
| 39 | + brew install patchutils |
| 40 | + cpan -i IPC::Run |
| 41 | + |
| 42 | +commit-patch is known to run on Linux and Mac OS X. It is perl, |
| 43 | +so ideally it will run anywhere, but we have never tested in |
| 44 | +other environments, most notably Windows. Use at your own risk. |
| 45 | + |
| 46 | +Instructions |
| 47 | +------------ |
| 48 | + |
| 49 | +- commit-patch: See the man page or perldoc: |
| 50 | + ``` |
| 51 | + man ./commit-patch.1 |
| 52 | + perldoc commit-patch |
| 53 | + ``` |
| 54 | + |
| 55 | +- commit-patch-buffer.el is an emacs interface to |
| 56 | + commit-patch. It allows you to just hit C-c C-c in any patch |
| 57 | + buffer to apply and commit only the changes indicated by the |
| 58 | + patch, regardless of the changes in your working directory. |
| 59 | + |
| 60 | + One method of working with commit-patch-buffer is to just M-x |
| 61 | + vc-diff a file then kill, split or edit the resulting hunks and |
| 62 | + to then hit C-c C-c to commit the patch. The other is to use |
| 63 | + PCL cvs mode to tag many files and then to diff them into a |
| 64 | + buffer which can again be edited and committed. |
| 65 | + |
| 66 | +Homepage |
| 67 | +-------- |
| 68 | +http://www.porkrind.org/commit-patch/ |
| 69 | + |
| 70 | +Authors |
| 71 | +------- |
| 72 | +- David Caldwell <[email protected]> |
| 73 | + |
| 74 | + |
| 75 | +Copyright and License |
| 76 | +--------------------- |
| 77 | +Copyright © 2003-2021 by David Caldwell and Jim Radford. |
| 78 | + |
| 79 | +`commit-patch` is distributed under the GNU General Public |
| 80 | +License. See the COPYING file in the distribution for more |
| 81 | +details. |
0 commit comments