/usr/share/doc/gnat-gps/html/Implementing-VCS-actions.html is in gnat-gps-doc 5.0-6.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 | <html lang="en">
<head>
<title>Implementing VCS actions - Using the GNAT Programming Studio</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Using the GNAT Programming Studio">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Adding-support-for-new-Version-Control-Systems.html#Adding-support-for-new-Version-Control-Systems" title="Adding support for new Version Control Systems">
<link rel="prev" href="Describing-a-VCS.html#Describing-a-VCS" title="Describing a VCS">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 2002-2010 AdaCore.
This document is free; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, see `http://www.gnu.org/licenses/'.-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
pre.smallexample {background-color:rgb(240,240,240);
font-family: courier new,courier,fixed;
font-size: 14px;
margin: 0px 40px 0px 40px;
border-width: 1px 2px 2px 1px;
border-top-style: dotted;
border-left-style: dotted;
border-right-style: solid;
border-bottom-style: solid;
border-color: black;}
code {color:black;
font-family: courier new,courier,fixed;
font-size: 14px;}
body {font-family: arial,helvetica,sans-serif;
font-size: 16px;
max-width: 800px;
text-align: justify}
samp {font-family: courier new,courier,fixed;
font-size: 14px}
--></style>
</head>
<body>
<div class="node">
<a name="Implementing-VCS-actions"></a>
<p>
Previous: <a rel="previous" accesskey="p" href="Describing-a-VCS.html#Describing-a-VCS">Describing a VCS</a>,
Up: <a rel="up" accesskey="u" href="Adding-support-for-new-Version-Control-Systems.html#Adding-support-for-new-Version-Control-Systems">Adding support for new Version Control Systems</a>
<hr>
</div>
<h4 class="subsection">16.9.3 Implementing VCS actions</h4>
<p class="noindent">A number of “standard” VCS operations are known to GPS. Each of
these operations can be implemented, using Actions. See <a href="Defining-Actions.html#Defining-Actions">Defining Actions</a>) for a complete description of how to implement actions.
<p>Here is a list of all the defined VCS operations, and their
parameters:
<dl>
<dt><code>status_files</code><dd>
<dl>
<dt><code>$1 = whether the log files should be cleared when obtaining up-to-date status</code> <br><dt><code>$2- = the list of files to query status for.</code><dd> </dl>
Query the status for a list of files. This should perform a complete
VCS query and return results as complete as possible.
<br><dt><code>status_dir</code><dd>
<dl>
<dt><code>$1 = the directory.</code><dd> </dl>
Same as above, but works on all the files in one directory.
<br><dt><code>status_dir_recursive</code><dd>
<dl>
<dt><code>$1 = the directory.</code><dd> </dl>
Same as above, but works on all the files in one directory and all
subdirectories, recursively.
<br><dt><code>local_status_files</code><dd>
<dl>
<dt><code>$* = list of files</code><dd> </dl>
Query the local status for specified files. This query should be as
fast as possible, not connecting to any remote VCS. The results need
not be complete, but it is not useful to implement this command if
the output does not contain at least the working revision.
<br><dt><code>open</code><dd>
<dl>
<dt><code>$* = list of files</code><dd> </dl>
Open files or directories for editing. This command should be
implemented on any VCS that require an explicit check-out/open/edit
action before being able to edit a file.
<br><dt><code>update</code><dd>
<dl>
<dt><code>$* = list of files</code><dd> </dl>
Bring the specified files in sync with the latest repository revision.
<br><dt><code>resolved</code><dd>
<dl>
<dt><code>$* = list of files</code><dd> </dl>
Mark files' merge conflics as resolved. Some version control systems
(like Subversion) will block any commit until this action is called.
<br><dt><code>commit</code><dd>
<dl>
<dt><code>$1 = log file</code> <br><dt><code>$2- = list of files</code><dd> </dl>
Commit/submit/check-in files or directories with provided log. The log is
passed in a file.
<br><dt><code>commit_dir</code><dd>
<dl>
<dt><code>$1 = log</code> <br><dt><code>$2 = directory</code><dd> </dl>
Commit/submit one directory with provided log. The log is passed in
a file.
<br><dt><code>history_text</code><dd>
<dl>
<dt><code>$1 = file</code><dd> </dl>
Query the entire changelog history for the specified file. The result
is expected to be placed into an editor as plain text.
<br><dt><code>history</code><dd>
<dl>
<dt><code>$1 = file</code><dd> </dl>
Query the entire changelog history for the specified file. The result
is expected to be placed into a Revision View.
<br><dt><code>history_revision</code><dd>
<dl>
<dt><code>$1 = revision</code> <br><dt><code>$2 = file</code><dd> </dl>
Query the history for corresponding revision of the specified file.
<br><dt><code>annotate</code><dd>
<dl>
<dt><code>$1 = file</code><dd> </dl>
Query the annotations for a file.
<br><dt><code>add</code><dd>
<dl>
<dt><code>$1 = log</code> <br><dt><code>$2- = list of files or dirs</code><dd> </dl>
Add files/dirs to the repository, with the provided revision log. The
added files/dirs are commited.
<br><dt><code>add_no_commit</code><dd>
<dl>
<dt><code>$1 = log</code> <br><dt><code>$2- = list of files or dirs</code><dd> </dl>
Add files/dirs to the repository, with the provided revision log. The
added files/dirs are not commited.
<br><dt><code>remove</code><dd>
<dl>
<dt><code>$1 = log</code> <br><dt><code>$2 = file or dir</code><dd> </dl>
Remove file/dir from the repository, with the provided revision log.
<br><dt><code>remove_no_commit</code><dd>
<dl>
<dt><code>$1 = log</code> <br><dt><code>$2 = file or dir</code><dd> </dl>
Remove file/dir from the repository, with the provided revision log.
The removed files/dirs are not commited.
<br><dt><code>revert</code><dd>
<dl>
<dt><code>$* = files</code><dd> </dl>
Revert the local file to repository revision, cancelling all local
changes, and close the file for editing if it was open.
<br><dt><code>diff_patch</code><dd>
<dl>
<dt><code>$1 = file</code><dd> </dl>
Create a textual diff for the given file. This command is used to
build the activity patch file.
<br><dt><code>diff_head</code><dd>
<dl>
<dt><code>$1 = file</code><dd> </dl>
Display a visual comparison between the local file and the latest
repository revision. The diff command must report a <i>normal</i> diff
as opposed to <i>context</i> or <i>unified</i> ones.
<br><dt><code>diff_base_head</code><dd>
<dl>
<dt><code>$1 = file</code><dd> </dl>
Display a visual comparison between the revision from which the file
has been checked-out and the latest revision. The diff command must
report a <i>normal</i> diff as opposed to <i>context</i> or <i>unified</i> ones.
<br><dt><code>diff_working</code><dd>
<dl>
<dt><code>$1 = file</code><dd> </dl>
Display a visual comparison between the local file and the revision
from which it was obtained. The diff command must report a <i>normal</i> diff
as opposed to <i>context</i> or <i>unified</i> ones.
<br><dt><code>diff</code><dd>
<dl>
<dt><code>$1 = rev</code> <br><dt><code>$2 = file</code><dd> </dl>
Display a visual comparison between the local file and the specified
revision. The diff command must report a <i>normal</i> diff
as opposed to <i>context</i> or <i>unified</i> ones.
<br><dt><code>diff2</code><dd>
<dl>
<dt><code>$1 = revision 1</code> <br><dt><code>$2 = revision 2</code> <br><dt><code>$3 = file</code><dd> </dl>
Display a visual comparison between the two specified revisions of
the file. The diff command must report a <i>normal</i> diff
as opposed to <i>context</i> or <i>unified</i> ones.
</dl>
<!-- -->
</body></html>
|