summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 5ee5f5a)
raw | patch | inline | side by side (parent: 5ee5f5a)
author | Jonathan Nieder <jrnieder@gmail.com> | |
Sun, 16 Jan 2011 02:22:35 +0000 (20:22 -0600) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 19 Jan 2011 00:51:13 +0000 (16:51 -0800) |
Omit needless words ("Additionally ... <path> may also" is redundant).
While at it, place the explanation of this special case after the
general rules for paths to provide the reader with some context.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
While at it, place the explanation of this special case after the
general rules for paths to provide the reader with some context.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-fast-import.txt | patch | blob | history |
index fed48bd7224b2a714cf04778e280ebf058991746..4415e636352ea88f34a798b6c29dc5e34d60d868 100644 (file)
If an `LF` or double quote must be encoded into `<path>` shell-style
quoting should be used, e.g. `"path/with\n and \" in it"`.
-Additionally, in `040000` mode, `<path>` may also be an empty string
-(`""`) to specify the root of the tree.
-
The value of `<path>` must be in canonical form. That is it must not:
* contain an empty directory component (e.g. `foo//bar` is invalid),
* contain the special component `.` or `..` (e.g. `foo/./bar` and
`foo/../bar` are invalid).
+The root of the tree can be represented by an empty string as `<path>`.
+
It is recommended that `<path>` always be encoded using UTF-8.
`filedelete`