From: Thomas Ackermann Date: Tue, 02 Apr 2013 09:28:44 GMT Subject: [PATCH 3/3] Remove definition of refspec and pathspec from glossary-content.txt Message-ID: <1622068154.727718.1364894924364.JavaMail.ngmail@webmail14.arcor-online.net> In-Reply-To: <1481339149.727628.1364894663266.JavaMail.ngmail@webmail14.arcor-online.net> Signed-off-by: Thomas Ackermann --- Documentation/glossary-content.txt | 65 ++------------------------------------ 1 file changed, 3 insertions(+), 62 deletions(-) diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt index 05bfebc..1c9c522 100644 --- a/Documentation/glossary-content.txt +++ b/Documentation/glossary-content.txt @@ -261,59 +261,7 @@ This commit is referred to as a "merge commit", or sometimes just a pack. [[def_pathspec]]pathspec:: - Pattern used to specify paths. -+ -Pathspecs are used on the command line of "git ls-files", "git -ls-tree", "git add", "git grep", "git diff", "git checkout", -and many other commands to -limit the scope of operations to some subset of the tree or -worktree. See the documentation of each command for whether -paths are relative to the current directory or toplevel. The -pathspec syntax is as follows: - -* any path matches itself -* the pathspec up to the last slash represents a - directory prefix. The scope of that pathspec is - limited to that subtree. -* the rest of the pathspec is a pattern for the remainder - of the pathname. Paths relative to the directory - prefix will be matched against that pattern using fnmatch(3); - in particular, '*' and '?' _can_ match directory separators. -+ -For example, Documentation/*.jpg will match all .jpg files -in the Documentation subtree, -including Documentation/chapter_1/figure_1.jpg. - -+ -A pathspec that begins with a colon `:` has special meaning. In the -short form, the leading colon `:` is followed by zero or more "magic -signature" letters (which optionally is terminated by another colon `:`), -and the remainder is the pattern to match against the path. The optional -colon that terminates the "magic signature" can be omitted if the pattern -begins with a character that cannot be a "magic signature" and is not a -colon. -+ -In the long form, the leading colon `:` is followed by a open -parenthesis `(`, a comma-separated list of zero or more "magic words", -and a close parentheses `)`, and the remainder is the pattern to match -against the path. -+ -The "magic signature" consists of an ASCII symbol that is not -alphanumeric. -+ --- -top `/`;; - The magic word `top` (mnemonic: `/`) makes the pattern match - from the root of the working tree, even when you are running - the command from inside a subdirectory. --- -+ -Currently only the slash `/` is recognized as the "magic signature", -but it is envisioned that we will support more types of magic in later -versions of Git. -+ -A pathspec with only a colon means "there is no pathspec". This form -should not be combined with other pathspec. + Pattern used to specify paths in Git commands. [[def_parent]]parent:: A <> contains a (possibly empty) list @@ -382,15 +330,8 @@ should not be combined with other pathspec. [[def_refspec]]refspec:: A "refspec" is used by <> and <> to describe the mapping between remote - <> and local ref. They are combined with a colon in - the format :, preceded by an optional plus sign, +. - For example: `git fetch $URL - refs/heads/master:refs/heads/origin` means "grab the master - <> <> from the $URL and store - it as my origin branch head". And `git push - $URL refs/heads/master:refs/heads/to-upstream` means "publish my - master branch head as to-upstream branch at $URL". See also - linkgit:git-push[1]. + <> and local ref. + See linkgit:git-push[1] for details. [[def_remote_tracking_branch]]remote-tracking branch:: A regular Git <> that is used to follow changes from -- 1.8.1.msysgit.1 --- Thomas