diff options
| author |  Junio C Hamano <junio@pobox.com> | 2008-12-07 18:38:46 -0800 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2008-12-09 19:06:15 -0800 |
| commit | aa971cb9bf4105eefb435b9e6f282f019529c35f (patch) | |
| tree | 2850f1c3006acb6a2365934e6ea2d4c2a6257402 /t/t5515/refs.br-config-explicit-merge_config-explicit | |
| parent | git-svn: Make following parents atomic (diff) | |
| download | tgif-aa971cb9bf4105eefb435b9e6f282f019529c35f.tar.xz | |
work around Python warnings from AsciiDoc
It appears that a reference to an anchor defined as [[anchor-name]] from
another place using <<anchor-name>> syntax, when the anchor name contains
a string "-with-" in its name, triggers these warnings from Python
interpreter.
asciidoc -b docbook -d book user-manual.txt
<string>:1: Warning: 'with' will become a reserved keyword in Python 2.6
<string>:1: Warning: 'with' will become a reserved keyword in Python 2.6
<string>:1: Warning: 'with' will become a reserved keyword in Python 2.6
<string>:1: Warning: 'with' will become a reserved keyword in Python 2.6
There currently is no reference to "Finding comments with given content",
but for consistency and for futureproofing, the anchor is also updated as
the other ones that are actually used and trigger these warnings.
Signed-off-by: Junio C Hamano <junio@pobox.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/refs.br-config-explicit-merge_config-explicit')
0 files changed, 0 insertions, 0 deletions