Mini Shell Moded By TiGER HeX
Home
||
Turbo Force
||
B-F Config_Cpanel
Current Path :
/
proc
/
self
/
root
/
usr
/
share
/
doc
/
commit-patch
/
Linux midnightridazz 4.19.0-11-cloud-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64
Upload File :
New :
File
Dir
//proc/self/root/usr/share/doc/commit-patch/commit-patch.html
<?xml version="1.0" ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>commit-patch Documentation</title> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <link rev="made" href="mailto:root@localhost" /> </head> <body> <ul id="index"> <li><a href="#NAME">NAME</a></li> <li><a href="#SYNOPSIS">SYNOPSIS</a></li> <li><a href="#DESCRIPTION">DESCRIPTION</a></li> <li><a href="#OPTIONS">OPTIONS</a></li> <li><a href="#DIAGNOSTICS">DIAGNOSTICS</a></li> <li><a href="#CAVEATS">CAVEATS</a></li> <li><a href="#EXAMPLES">EXAMPLES</a></li> <li><a href="#AUTHORS">AUTHORS</a></li> <li><a href="#COPYRIGHT-AND-LICENSE">COPYRIGHT AND LICENSE</a></li> <li><a href="#HISTORY">HISTORY</a></li> </ul> <h1 id="NAME">NAME</h1> <p>commit-patch - commit patches to <i>Darcs</i>, <i>Git</i>, <i>Mercurial</i>, <i>Bazaar</i>, <i>Monotone</i>, <i>Subversion</i>, or <i>CVS</i> repositories</p> <h1 id="SYNOPSIS">SYNOPSIS</h1> <p>commit-patch [<b>--amend</b>] [<b>-m</b> <i>message</i>] [<b>-F</b> <i>message-file</i>] [<b>-v</b>] [<b>--dry-run</b>] [<i>patch-file</i>]</p> <p>commit-partial [<b>--amend</b>] [<b>-v</b>] [<b>--dry-run</b>] [<b>--retry</b>] [<i>file</i> ...]</p> <h1 id="DESCRIPTION">DESCRIPTION</h1> <p>Normally version control systems don't allow fine grained commits. <b>commit-patch</b> allows the user to control <i>exactly</i> what gets committed (or "recorded", in <i>Darcs</i> parlance) by letting the user supply a patch to be committed rather than using the files in the current working directory. If <i>patch-file</i> is not supplied on the command line then the patch will be read from standard input.</p> <p><b>commit-partial</b> is like commit-patch except that it will create a patch from the current changes in the current working directory and launch your editor so that you can edit the patch and the commit message (using the <b>VISUAL</b> environment variable, or if that isn't set the <b>EDITOR</b> environment variable, or, if <i>that</i> isn't set, <b>vi</b>. Any files you specify will be passed to your version control's diff command.</p> <p><b>commit-patch</b> currently supports the following version control systems: <b><i>Darcs</i></b>, <b><i>Git</i></b>, <b><i>Mercurial</i></b>, <b><i>Bazaar</i></b>, <b><i>Monotone</i></b>, <b><i>Subversion</i></b>, and <b><i>CVS</i></b>.</p> <h1 id="OPTIONS">OPTIONS</h1> <p><b>-a</b>, <b>--amend</b> - Amend a previous commit. Currently only <b><i>Darcs</i></b> and <b><i>Git</i></b> support this option. When used with <b><i>Git</i></b> it will amend the previous commit. When used with <b><i>Darcs</i></b>, <b><i>Darcs</i></b> will ask you which patch you want to amend.</p> <p><b>-m</b>, <b>--message</b>=<i>message</i> - An optional <i>message</i> to use as the commit text. If the message is multiple lines then <i>Darcs</i>, <i>Git</i>, and <i>Mercurial</i> will use the first line as the patch name and the rest as commit details. If the <code>-m</code> option is not specified then the result will be the same as whatever the underlying version control system would do if you didn't specify a message name on the command line. That is, <b>commit-patch</b> does not interfere with the patch naming process of the underlying version control system; <i>Darcs</i> will still ask you interactively; <i>CVS</i> and <i>Subversion</i> will still launch your editor.</p> <p><b>-F</b>, <b>--message-file</b>=<i>filename</i> - You can optionally get the commit message from a file. This is generally only useful for scripting <b>commit-patch</b>.</p> <p><b>-v</b>, <b>--verbose</b> - Turn on debugging. This will print the commands that <b>commit-patch</b> is running to get the patch committed.</p> <p><b>-n</b>, <b>--dry-run</b> - Turn on more paranoid debugging. This will print the commands that <b>commit-patch</b> will run to get the patch committed but it won't actually run those commands.</p> <p><b>-r</b>, <b>--retry</b> - Only available in <i>commit-partial</i>. This will reload the last patch that was attempted to be committed into your editor instead of the current changes in the directory. This is for cases where the patch fails to commit for some reason and you want to try to fix it instead of starting over.</p> <h1 id="DIAGNOSTICS">DIAGNOSTICS</h1> <p><b>commit-patch</b> works by manipulating the working directory using <code>patch</code>, <code>interdiff</code>, and the underlying version control system's <code>diff</code>. If any part of the process fails, <b>commit-patch</b> will attempt to restore the working directory to the state it was before the command was run. Any errors from the underlying version control system or from patch will be printed.</p> <h1 id="CAVEATS">CAVEATS</h1> <p>The patch specified on the command line must originate from the same place as the current directory. That is, the following will not work:</p> <pre><code> cvs diff -u > ../a.patch cd .. commit-patch a.patch</code></pre> <p>You <b>must</b> run <b>commit-patch</b> from the same directory that the original patch was based from.</p> <p><i>Darcs</i>, <i>Git</i> and <i>Mercurial</i> put <code>a/</code> and <code>b/</code> in front of all the paths in the diff output. Don't worry about this; <b>commit-patch</b> takes it into account.</p> <h1 id="EXAMPLES">EXAMPLES</h1> <p>Typical <i>CVS</i> usage:</p> <pre><code> cvs diff -u > a.patch emacs a.patch commit-patch a.patch</code></pre> <p><i>Mercurial</i> usage with a message specified:</p> <pre><code> hg diff > a.patch emacs a.patch commit-patch -m "This is a commit message" a.patch</code></pre> <p><i>Darcs</i> usage with a multi-line message specified:</p> <pre><code> darcs diff -u > a.patch emacs a.patch commit-patch -m 'This is the patch name Here are the patch details' a.patch</code></pre> <h1 id="AUTHORS">AUTHORS</h1> <ul> <li><p>David Caldwell <david@porkrind.org></p> </li> <li><p>Jim Radford <radford@blackbean.org></p> </li> </ul> <h1 id="COPYRIGHT-AND-LICENSE">COPYRIGHT AND LICENSE</h1> <p>Copyright © 2003-2015 by David Caldwell and Jim Radford.</p> <p><b>commit-patch</b> is distributed under the GNU General Public License. See the COPYING file in the distribution for more details.</p> <h1 id="HISTORY">HISTORY</h1> <p><b>commit-patch</b> was originally called <code>cvs-commit-patch</code> and was a bash script written in 2003 by Jim Radford (with David Caldwell in the room drawing the procedure on a white board). David later converted it do <code>darcs-commit-patch</code>, then integrated them back together into <b>commit-patch</b>. <i>Mercurial</i> support was then added. At some point David translated from bash into perl because funky bash quoting issues were causing problems with a repository that had a space in one of the directory names.</p> </body> </html>