<em>git-config</em> [--global] [type] --get-all name [value_regex]\r
<em>git-config</em> [--global] [type] --unset name [value_regex]\r
<em>git-config</em> [--global] [type] --unset-all name [value_regex]\r
+<em>git-config</em> [--global] [type] --rename-section old_name new_name\r
+<em>git-config</em> [--global] [type] --remove-section name\r
<em>git-config</em> [--global] -l | --list</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
</p>\r
</dd>\r
<dt>\r
+--remove-section\r
+</dt>\r
+<dd>\r
+<p>\r
+ Remove the given section from the configuration file.\r
+</p>\r
+</dd>\r
+<dt>\r
+--rename-section\r
+</dt>\r
+<dd>\r
+<p>\r
+ Rename the given section to a new name.\r
+</p>\r
+</dd>\r
+<dt>\r
--unset\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 05-Mar-2007 02:37:02 UTC\r
+Last updated 09-Mar-2007 09:06:21 UTC\r
</div>\r
</div>\r
</body>\r
'git-config' [--global] [type] --get-all name [value_regex]
'git-config' [--global] [type] --unset name [value_regex]
'git-config' [--global] [type] --unset-all name [value_regex]
+'git-config' [--global] [type] --rename-section old_name new_name
+'git-config' [--global] [type] --remove-section name
'git-config' [--global] -l | --list
DESCRIPTION
--global::
Use global ~/.gitconfig file rather than the repository .git/config.
+--remove-section::
+ Remove the given section from the configuration file.
+
+--rename-section::
+ Rename the given section to a new name.
+
--unset::
Remove the line matching the key from config file.
Dumps the internal marks table to <file> when complete.\r
Marks are written one per line as <tt>:markid SHA-1</tt>.\r
Frontends can use this file to validate imports after they\r
- have been completed.\r
+ have been completed, or to save the marks table across\r
+ incremental runs. As <file> is only opened and truncated\r
+ at checkpoint (or completion) the same path can also be\r
+ safely given to --import-marks.\r
+</p>\r
+</dd>\r
+<dt>\r
+--import-marks=<file>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Before processing any input, load the marks specified in\r
+ <file>. The input file must exist, must be readable, and\r
+ must use the same format as produced by --export-marks.\r
+ Multiple options may be supplied to import more than one\r
+ set of marks. If a mark is defined to different values,\r
+ the last file wins.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 14-Feb-2007 07:23:34 UTC\r
+Last updated 09-Mar-2007 09:06:22 UTC\r
</div>\r
</div>\r
</body>\r
Dumps the internal marks table to <file> when complete.
Marks are written one per line as `:markid SHA-1`.
Frontends can use this file to validate imports after they
- have been completed.
+ have been completed, or to save the marks table across
+ incremental runs. As <file> is only opened and truncated
+ at checkpoint (or completion) the same path can also be
+ safely given to \--import-marks.
+
+--import-marks=<file>::
+ Before processing any input, load the marks specified in
+ <file>. The input file must exist, must be readable, and
+ must use the same format as produced by \--export-marks.
+ Multiple options may be supplied to import more than one
+ set of marks. If a mark is defined to different values,
+ the last file wins.
--export-pack-edges=<file>::
After creating a packfile, print a line of data to
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Mar-2007 02:42:39 UTC\r
+Last updated 09-Mar-2007 09:06:24 UTC\r
</div>\r
</div>\r
</body>\r