git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] Documentation: git-svn: fix spurious bolding that mangles the output

From
Jeff King <peff@peff.net>
Date
Apr 22, 2009, 15:15 UTC
Message-ID
<20090422151515.GA12370@coredump.intra.peff.net>
In-Reply-To
<1240411907-5002-1-git-send-email-wjl@icecavern.net>
On Wed, Apr 22, 2009 at 08:51:46AM -0600, Wesley J. Landaker wrote:
Show 7 quoted lines
> Without this fix, the output looks like:
> 
> "Keep in mind that the  (asterisk) wildcard of the local ref (right of
> the :) *must be the ..." -- with half the sentence spuriously bold.
> 
> This is probably working around an asciidoc bug, but it's better to fix
> this than to leave the documentation in an unreadable state.

I think it's a documentation bug; the asterisk is a special character, so it is seeing the first one as the start of bold, instead of the one on the left side of *must*.

>  Keep in mind that the '*' (asterisk) wildcard of the local ref
> -(right of the ':') *must* be the farthest right path component;
> +(right of the ':') must be the farthest right path component;

So the right fix is probably to quote the asterisk that is not part of the bolding, like:

diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 9229d45..3e22e40 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -693,7 +693,7 @@ listed below are allowed:
 	tags = tags/*/project-a:refs/remotes/project-a/tags/*
 ------------------------------------------------------------------------
 
-Keep in mind that the '*' (asterisk) wildcard of the local ref
+Keep in mind that the '\*' (asterisk) wildcard of the local ref
 (right of the ':') *must* be the farthest right path component;
 however the remote wildcard may be anywhere as long as it's own
 independent path component (surrounded by '/' or EOL).   This
Previous: Wesley J. LandakerNext: Wesley J. Landaker
Message 3 of 6 in “Documentation: git-svn: fix spurious bolding that mangles the output”
  1. 1/2 Documentation: git-svn: fix spurious bolding that mangles the outputWesley J. Landaker, Apr 22, 2009
  2. 2/2 Documentation: git-svn: fix a grammatical error without awkwardnessWesley J. Landaker, Apr 22, 2009
  3. Jeff KingApr 22, 2009
  4. 1/2 Documentation: git-svn: fix spurious bolding that mangles the outputWesley J. Landaker, Apr 22, 2009
  5. Junio C HamanoApr 23, 2009
  6. 2/2 Documentation: git-svn: fix a grammatical error without awkwardnessWesley J. Landaker, Apr 22, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.