See gitlink:git-show-branch[1].
tar.umask::
- By default, gitlink:git-tar-tree[1] sets file and directories modes
- to 0666 or 0777. While this is both useful and acceptable for projects
- such as the Linux Kernel, it might be excessive for other projects.
- With this variable, it becomes possible to tell
- gitlink:git-tar-tree[1] to apply a specific umask to the modes above.
- The special value "user" indicates that the user's current umask will
- be used. This should be enough for most projects, as it will lead to
- the same permissions as gitlink:git-checkout[1] would use. The default
- value remains 0, which means world read-write.
+ This variable can be used to restrict the permission bits of
+ tar archive entries. The default is 0002, which turns off the
+ world write bit. The special value "user" indicates that the
+ archiving user's umask will be used instead. See umask(2) and
+ gitlink:git-archive[1].
user.email::
Your email address to be recorded in any newly created commits.
</div>\r
<h2>CONFIGURATION</h2>\r
<div class="sectionbody">\r
-<p>By default, file and directories modes are set to 0666 or 0777 in tar\r
-archives. It is possible to change this by setting the "umask" variable\r
-in the repository configuration as follows :</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt>umask = 002 ;# group friendly</tt></pre>\r
-</div></div>\r
-<p>The special umask value "user" indicates that the user's current umask\r
-will be used instead. The default value remains 0, which means world\r
-readable/writable files and directories.</p>\r
+<dl>\r
+<dt>\r
+tar.umask\r
+</dt>\r
+<dd>\r
+<p>\r
+ This variable can be used to restrict the permission bits of\r
+ tar archive entries. The default is 0002, which turns off the\r
+ world write bit. The special value "user" indicates that the\r
+ archiving user's umask will be used instead. See umask(2) for\r
+ details.\r
+</p>\r
+</dd>\r
+</dl>\r
</div>\r
<h2>EXAMPLES</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:31 UTC\r
+Last updated 23-Aug-2007 00:24:02 UTC\r
</div>\r
</div>\r
</body>\r
CONFIGURATION
-------------
-By default, file and directories modes are set to 0666 or 0777 in tar
-archives. It is possible to change this by setting the "umask" variable
-in the repository configuration as follows :
-[tar]
- umask = 002 ;# group friendly
-
-The special umask value "user" indicates that the user's current umask
-will be used instead. The default value remains 0, which means world
-readable/writable files and directories.
+tar.umask::
+ This variable can be used to restrict the permission bits of
+ tar archive entries. The default is 0002, which turns off the
+ world write bit. The special value "user" indicates that the
+ archiving user's umask will be used instead. See umask(2) for
+ details.
EXAMPLES
--------
</dt>\r
<dd>\r
<p>\r
- By default, <a href="git-tar-tree.html">git-tar-tree(1)</a> sets file and directories modes\r
- to 0666 or 0777. While this is both useful and acceptable for projects\r
- such as the Linux Kernel, it might be excessive for other projects.\r
- With this variable, it becomes possible to tell\r
- <a href="git-tar-tree.html">git-tar-tree(1)</a> to apply a specific umask to the modes above.\r
- The special value "user" indicates that the user's current umask will\r
- be used. This should be enough for most projects, as it will lead to\r
- the same permissions as <a href="git-checkout.html">git-checkout(1)</a> would use. The default\r
- value remains 0, which means world read-write.\r
+ This variable can be used to restrict the permission bits of\r
+ tar archive entries. The default is 0002, which turns off the\r
+ world write bit. The special value "user" indicates that the\r
+ archiving user's umask will be used instead. See umask(2) and\r
+ <a href="git-archive.html">git-archive(1)</a>.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 21-Aug-2007 02:20:17 UTC\r
+Last updated 23-Aug-2007 00:24:02 UTC\r
</div>\r
</div>\r
</body>\r
taken from the reflog. By default, <em>commit@{Nth}</em> notation is\r
used in the output. When the starting commit is specified as\r
instead. Under <em>--pretty=oneline</em>, the commit message is\r
-prefixed with this information on the same line.<br />\r
-Cannot be combined with --reverse.\r
+prefixed with this information on the same line.\r
</p>\r
+<p>Cannot be combined with <em>--reverse</em>.</p>\r
</dd>\r
<dt>\r
--merge\r
<dd>\r
<p>\r
Output the commits in reverse order.\r
- Cannot be combined with --walk-reflogs.\r
+ Cannot be combined with <em>--walk-reflogs</em>.\r
</p>\r
</dd>\r
</dl>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 21-Aug-2007 02:20:19 UTC\r
+Last updated 23-Aug-2007 00:24:04 UTC\r
</div>\r
</div>\r
</body>\r
'commit@{now}', output also uses 'commit@\{timestamp}' notation
instead. Under '\--pretty=oneline', the commit message is
prefixed with this information on the same line.
-+
-Cannot be combined with --reverse.
+
+Cannot be combined with '\--reverse'.
--merge::
--reverse::
Output the commits in reverse order.
- Cannot be combined with --walk-reflogs.
+ Cannot be combined with '\--walk-reflogs'.
Object Traversal
~~~~~~~~~~~~~~~~
history of the directory that it is tracking, however (much like\r
how <em>svn log</em> works).</p>\r
</div>\r
+<h2>CAVEATS</h2>\r
+<div class="sectionbody">\r
+<p>For the sake of simplicity and interoperating with a less-capable system\r
+(SVN), it is recommended that all git-svn users clone, fetch and dcommit\r
+directly from the SVN server, and avoid all git-clone/pull/merge/push\r
+operations between git repositories and branches. The recommended\r
+method of exchanging code between git branches and users is\r
+git-format-patch and git-am, or just dcommiting to the SVN repository.</p>\r
+<p>Running <em>git-merge</em> or <em>git-pull</em> is NOT recommended on a branch you\r
+plan to dcommit from. Subversion does not represent merges in any\r
+reasonable or useful fashion; so users using Subversion cannot see any\r
+merges you've made. Furthermore, if you merge or pull from a git branch\r
+that is a mirror of an SVN branch, dcommit may commit to the wrong\r
+branch.</p>\r
+<p><em>git-clone</em> does not clone branches under the refs/remotes/ hierarchy or\r
+any git-svn metadata, or config. So repositories created and managed with\r
+using git-svn should use rsync(1) for cloning, if cloning is to be done\r
+at all.</p>\r
+<p>Since <em>dcommit</em> uses rebase internally, any git branches you git-push to\r
+before dcommit on will require forcing an overwrite of the existing ref\r
+on the remote repository. This is generally considered bad practice,\r
+see the git-push(1) documentation for details.</p>\r
+<p>Do not use the --amend option of git-commit(1) on a change you've\r
+already dcommitted. It is considered bad practice to --amend commits\r
+you've already pushed to a remote repository for other users, and\r
+dcommit with SVN is analogous to that.</p>\r
+</div>\r
<h2>BUGS</h2>\r
<div class="sectionbody">\r
<p>We ignore all SVN properties except svn:executable. Any unhandled\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Aug-2007 06:05:54 UTC\r
+Last updated 23-Aug-2007 00:24:06 UTC\r
</div>\r
</div>\r
</body>\r
history of the directory that it is tracking, however (much like
how 'svn log' works).
+CAVEATS
+-------
+
+For the sake of simplicity and interoperating with a less-capable system
+(SVN), it is recommended that all git-svn users clone, fetch and dcommit
+directly from the SVN server, and avoid all git-clone/pull/merge/push
+operations between git repositories and branches. The recommended
+method of exchanging code between git branches and users is
+git-format-patch and git-am, or just dcommiting to the SVN repository.
+
+Running 'git-merge' or 'git-pull' is NOT recommended on a branch you
+plan to dcommit from. Subversion does not represent merges in any
+reasonable or useful fashion; so users using Subversion cannot see any
+merges you've made. Furthermore, if you merge or pull from a git branch
+that is a mirror of an SVN branch, dcommit may commit to the wrong
+branch.
+
+'git-clone' does not clone branches under the refs/remotes/ hierarchy or
+any git-svn metadata, or config. So repositories created and managed with
+using git-svn should use rsync(1) for cloning, if cloning is to be done
+at all.
+
+Since 'dcommit' uses rebase internally, any git branches you git-push to
+before dcommit on will require forcing an overwrite of the existing ref
+on the remote repository. This is generally considered bad practice,
+see the git-push(1) documentation for details.
+
+Do not use the --amend option of git-commit(1) on a change you've
+already dcommitted. It is considered bad practice to --amend commits
+you've already pushed to a remote repository for other users, and
+dcommit with SVN is analogous to that.
+
BUGS
----
</p>\r
</dd>\r
<dt>\r
+-u\r
+</dt>\r
+<dd>\r
+<p>\r
+ Replace underscores in tag names with periods.\r
+</p>\r
+</dd>\r
+<dt>\r
-I <ignorefile_name>\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:57 UTC\r
+Last updated 23-Aug-2007 00:24:06 UTC\r
</div>\r
</div>\r
</body>\r
Prepend 'rX: ' to commit messages, where X is the imported
subversion revision.
+-u::
+ Replace underscores in tag names with periods.
+
-I <ignorefile_name>::
Import the svn:ignore directory property to files with this
name in each directory. (The Subversion and GIT ignore
</div>\r
<h2>CONFIGURATION</h2>\r
<div class="sectionbody">\r
-<p>By default, file and directories modes are set to 0666 or 0777. It is\r
-possible to change this by setting the "umask" variable in the\r
-repository configuration as follows :</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt>umask = 002 ;# group friendly</tt></pre>\r
-</div></div>\r
-<p>The special umask value "user" indicates that the user's current umask\r
-will be used instead. The default value is 002, which means group\r
-readable/writable files and directories.</p>\r
+<dl>\r
+<dt>\r
+tar.umask\r
+</dt>\r
+<dd>\r
+<p>\r
+ This variable can be used to restrict the permission bits of\r
+ tar archive entries. The default is 0002, which turns off the\r
+ world write bit. The special value "user" indicates that the\r
+ archiving user's umask will be used instead. See umask(2) for\r
+ details.\r
+</p>\r
+</dd>\r
+</dl>\r
</div>\r
<h2>EXAMPLES</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:57 UTC\r
+Last updated 23-Aug-2007 00:24:08 UTC\r
</div>\r
</div>\r
</body>\r
CONFIGURATION
-------------
-By default, file and directories modes are set to 0666 or 0777. It is
-possible to change this by setting the "umask" variable in the
-repository configuration as follows :
-[tar]
- umask = 002 ;# group friendly
-
-The special umask value "user" indicates that the user's current umask
-will be used instead. The default value is 002, which means group
-readable/writable files and directories.
+tar.umask::
+ This variable can be used to restrict the permission bits of
+ tar archive entries. The default is 0002, which turns off the
+ world write bit. The special value "user" indicates that the
+ archiving user's umask will be used instead. See umask(2) for
+ details.
EXAMPLES
--------
projects / git.git / commitdiff