summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
c20b20a)
The link macro rename in
760a7cfc ("Documentation: Rename link
macros") missed the htmllink and manlink macros, resulting in broken
links in the docs if built with AsciiDoc 8.2.3 or later. This patch
renames manlink to linkman, and replaces htmllink with just link
(which is built-in).
Signed-off-by: Karl Wiberg <kha@treskal.com>
endif::backend-docbook[]
endif::doctype-manpage[]
endif::backend-docbook[]
endif::doctype-manpage[]
-# Usage: htmllink:url[text]
-
-ifdef::backend-docbook[]
-[htmllink-inlinemacro]
-{0}
-endif::backend-docbook[]
-
-ifdef::backend-xhtml11[]
-[htmllink-inlinemacro]
-<a href="{target}">{0}</a>
-endif::backend-xhtml11[]
-
-## manlink: macro
-#
-# Usage: manlink:command[manpage-section]
+# Usage: linkman:command[manpage-section]
#
# Note, {0} is the manpage section, while {target} is the command.
#
#
# Note, {0} is the manpage section, while {target} is the command.
#
# show the command.
ifdef::backend-docbook[]
# show the command.
ifdef::backend-docbook[]
{0%{target}}
{0#<citerefentry>}
{0#<refentrytitle>{target}</refentrytitle><manvolnum>{0}</manvolnum>}
{0%{target}}
{0#<citerefentry>}
{0#<refentrytitle>{target}</refentrytitle><manvolnum>{0}</manvolnum>}
endif::backend-docbook[]
ifdef::backend-xhtml11[]
endif::backend-docbook[]
ifdef::backend-xhtml11[]
<a href="{target}.html">{target}{0?({0})}</a>
endif::backend-xhtml11[]
<a href="{target}.html">{target}{0?({0})}</a>
endif::backend-xhtml11[]
Git commits into StGit patches after the fact -- and
linkstgsub:commit[], its inverse.
Git commits into StGit patches after the fact -- and
linkstgsub:commit[], its inverse.
-For more information, see htmllink:tutorial.html[the tutorial].
+For more information, see link:tutorial.html[the tutorial].
Specifying patches
~~~~~~~~~~~~~~~~~~
Specifying patches
~~~~~~~~~~~~~~~~~~
CONFIGURATION MECHANISM
-----------------------
CONFIGURATION MECHANISM
-----------------------
-StGit uses the same configuration mechanism as Git. See manlink:git[7]
+StGit uses the same configuration mechanism as Git. See linkman:git[7]
for more details.
TEMPLATES
for more details.
TEMPLATES
##############
StGit is a command-line application that provides functionality
##############
StGit is a command-line application that provides functionality
-similar to htmllink:http://savannah.nongnu.org/projects/quilt/[Quilt]
+similar to link:http://savannah.nongnu.org/projects/quilt/[Quilt]
(i.e. pushing/popping patches to/from a stack), but using Git instead
of +diff+ and +patch+. StGit stores its patches in a Git repository as
normal Git commits, and provides a number of commands to manipulate
(i.e. pushing/popping patches to/from a stack), but using Git instead
of +diff+ and +patch+. StGit stores its patches in a Git repository as
normal Git commits, and provides a number of commands to manipulate
This tutorial assumes you are already familiar with the basics of Git
(for example, branches, commits, and conflicts). For more information
This tutorial assumes you are already familiar with the basics of Git
(for example, branches, commits, and conflicts). For more information
-on Git, see manlink:git[1] or htmllink:http://git.or.cz/[the Git home
+on Git, see linkman:git[1] or link:http://git.or.cz/[the Git home
-(The documentation is also available in htmllink:stg.html[HTML
+(The documentation is also available in link:stg.html[HTML
finally:
(I'm assuming you're already familiar with
finally:
(I'm assuming you're already familiar with
-htmllink:http://en.wikipedia.org/wiki/Diff#Unified_format[unified
+link:http://en.wikipedia.org/wiki/Diff#Unified_format[unified
diff] patches like this from Git, but it's really quite simple; in
this example, I've added the +$$print 'My first patch!'$$+ line to the
file +stgit/main.py+, at around line 171.)
Since the patch is also a regular Git commit, you can also look at it
diff] patches like this from Git, but it's really quite simple; in
this example, I've added the +$$print 'My first patch!'$$+ line to the
file +stgit/main.py+, at around line 171.)
Since the patch is also a regular Git commit, you can also look at it
-with regular Git tools such as manlink:gitk[].
+with regular Git tools such as linkman:gitk[].
Creating another patch
----------------------
Creating another patch
----------------------
The minus sign says that +credit+ is 'unapplied' -- this means that
it's been temporarily put aside. If you look at the +AUTHORS+ file,
you'll see that our change to it is gone; and tools such as
The minus sign says that +credit+ is 'unapplied' -- this means that
it's been temporarily put aside. If you look at the +AUTHORS+ file,
you'll see that our change to it is gone; and tools such as
-manlink:gitk[] will not show it, because it's been edited out of the
+linkman:gitk[] will not show it, because it's been edited out of the
Git history. But it's just one linkstg:push[] command away from being
restored:
Git history. But it's just one linkstg:push[] command away from being
restored:
o.write_asciidoc(f)
f.write('\n')
_write_underlined('StGit', '-', f)
o.write_asciidoc(f)
f.write('\n')
_write_underlined('StGit', '-', f)
- f.write('Part of the StGit suite - see manlink:stg[1]\n')
+ f.write('Part of the StGit suite - see linkman:stg[1]\n')
def sign_options():
def callback(option, opt_str, value, parser, sign_str):
def sign_options():
def callback(option, opt_str, value, parser, sign_str):