mirror of
https://github.com/git/git
synced 2024-11-05 18:59:29 +00:00
5162e69732
Between AsciiDoc 8.2.2 and 8.2.3, the following change was made to the stock Asciidoc configuration: @@ -149,7 +153,10 @@ # Inline macros. # Backslash prefix required for escape processing. # (?s) re flag for line spanning. -(?su)[\\]?(?P<name>\w(\w|-)*?):(?P<target>\S*?)(\[(?P<attrlist>.*?)\])= + +# Explicit so they can be nested. +(?su)[\\]?(?P<name>(http|https|ftp|file|mailto|callto|image|link)):(?P<target>\S*?)(\[(?P<attrlist>.*?)\])= + # Anchor: [[[id]]]. Bibliographic anchor. (?su)[\\]?\[\[\[(?P<attrlist>[\w][\w-]*?)\]\]\]=anchor3 # Anchor: [[id,xreflabel]] This default regex now matches explicit values, and unfortunately in this case gitlink was being matched by just 'link', causing the wrong inline macro template to be applied. By renaming the macro, we can avoid being matched by the wrong regex. Signed-off-by: Dan McGee <dpmcgee@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
55 lines
1.7 KiB
Text
55 lines
1.7 KiB
Text
git-check-ref-format(1)
|
|
=======================
|
|
|
|
NAME
|
|
----
|
|
git-check-ref-format - Make sure ref name is well formed
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git-check-ref-format' <refname>
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
Checks if a given 'refname' is acceptable, and exits non-zero if
|
|
it is not.
|
|
|
|
A reference is used in git to specify branches and tags. A
|
|
branch head is stored under `$GIT_DIR/refs/heads` directory, and
|
|
a tag is stored under `$GIT_DIR/refs/tags` directory. git
|
|
imposes the following rules on how refs are named:
|
|
|
|
. It can include slash `/` for hierarchical (directory)
|
|
grouping, but no slash-separated component can begin with a
|
|
dot `.`;
|
|
|
|
. It cannot have two consecutive dots `..` anywhere;
|
|
|
|
. It cannot have ASCII control character (i.e. bytes whose
|
|
values are lower than \040, or \177 `DEL`), space, tilde `~`,
|
|
caret `{caret}`, colon `:`, question-mark `?`, asterisk `*`,
|
|
or open bracket `[` anywhere;
|
|
|
|
. It cannot end with a slash `/`.
|
|
|
|
These rules makes it easy for shell script based tools to parse
|
|
refnames, pathname expansion by the shell when a refname is used
|
|
unquoted (by mistake), and also avoids ambiguities in certain
|
|
refname expressions (see linkgit:git-rev-parse[1]). Namely:
|
|
|
|
. double-dot `..` are often used as in `ref1..ref2`, and in some
|
|
context this notation means `{caret}ref1 ref2` (i.e. not in
|
|
ref1 and in ref2).
|
|
|
|
. tilde `~` and caret `{caret}` are used to introduce postfix
|
|
'nth parent' and 'peel onion' operation.
|
|
|
|
. colon `:` is used as in `srcref:dstref` to mean "use srcref\'s
|
|
value and store it in dstref" in fetch and push operations.
|
|
It may also be used to select a specific object such as with
|
|
linkgit:git-cat-file[1] "git-cat-file blob v1.3.3:refs.c".
|
|
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[7] suite
|