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

Re: [PATCH] git-push.txt: describe how to default to pushing only current branch

From
Jeff King <peff@peff.net>
Date
Mar 17, 2009, 07:46 UTC
Message-ID
<20090317074633.GB18475@coredump.intra.peff.net>
In-Reply-To
<1237085349-14824-1-git-send-email-chris_johnsen@pobox.com>
On Sat, Mar 14, 2009 at 09:49:09PM -0500, Chris Johnsen wrote:
Show 9 quoted lines
> 1) literals that contain a double quote
> 
> 	$ git grep '`[^`]*"[^`]`' | cat
> 	config.txt:You can have `[section]` if you have `[section "subsection"]`, but you
> 
>    There might be a better regexp to find these, I did not think
>    about it too long. The above "hit" seems like a reasonable
>    literal string. Maybe it is OK to live with this one
>    ("[section "subsection"]").

Hmm, good point. Something with typeface that could not be in the string contents would probably be a better choice. The linkgit: links appear bolded. We could do that. We could also try underlining, though that might be hard to read if any strings contained underscores.

I tried to find examples of other manpages that faced the same problem. I would guess that bold is the best bet (for example, the 'cat' manpage on my system looks like (excuse my fake markup):

  -A, --show-all
      equivalent to <b>-vET</b>
Show 8 quoted lines
> 2) manpage-1.72.xsl 
> 
>    I have been setting DOCBOOK_XSL_172 to avoid the ".ft" problem
>    (<http://article.gmane.org/gmane.comp.version-control.git/112943>;
>    my system is Mac OS X 10.4.11 with MacPorts asciidoc 8.3.1,
>    xmlto version 0.0.21, and docbook-xsl 1.74.0). Since non-null
>    DOCBOOK_XSL_172 replaces callouts.xsl with manpage-1.72.xsl, I
>    added the line to manpage-1.72.xsl.

The "callouts" XSL is obviously becoming more than that (there is already a "I know, this is not a callout, but where else to put it?" comment in it). It probably makes sense to rename it to manpage.xsl (or even manpage-1.8.xsl), factor out common parts to manpage-base.xsl, and then include the -base version from both manpage and manpage-1.72.xsl.

Want to do a patch?
-Peff
Previous: Chris JohnsenNext: Junio C Hamano
Message 23 of 27 in “Not pushing all branches?”
  1. Peter KreftingMar 13, 2009
  2. Imran M YousufMar 13, 2009
  3. Peter KreftingMar 13, 2009
  4. Johannes SchindelinMar 13, 2009
  5. Finn Arne GangstadMar 13, 2009
  6. John TapsellMar 13, 2009
  7. Johannes SchindelinMar 13, 2009
  8. John TapsellMar 13, 2009
  9. Johannes SchindelinMar 13, 2009
  10. John TapsellMar 13, 2009
  11. Michael J GruberMar 13, 2009
  12. Johannes SchindelinMar 13, 2009
  13. Junio C HamanoMar 13, 2009
  14. Miles BaderMar 14, 2009
  15. Jeff KingMar 17, 2009
  16. Jeff KingMar 13, 2009
  17. git-push.txt: describe how to default to pushing only current branchChris Johnsen, Mar 14, 2009
  18. Junio C HamanoMar 14, 2009
  19. Jeff KingMar 14, 2009
  20. Jeff KingMar 14, 2009
  21. Chris JohnsenMar 15, 2009
  22. Chris JohnsenMar 15, 2009
  23. Jeff KingMar 17, 2009
  24. Junio C HamanoMar 14, 2009
  25. Jeff KingMar 14, 2009
  26. Junio C HamanoMar 16, 2009
  27. git-push.txt: describe how to default to pushing only current branchChris Johnsen, Mar 15, 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.