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

Re: [Patch v2 5/8] Prerequisites for creating nice html for all files in Documentation/howto

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 11, 2012, 19:06 UTC
Message-ID
<7vfw5k7rs5.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1873679011.46972.1349976139154.JavaMail.ngmail@webmail22.arcor-online.net>
Thomas Ackermann <th.acker66@arcor.de> writes:
Show 5 quoted lines
>>From 2b9538990e30ae0911117c8e3d8b6891c9de31cf Mon Sep 17 00:00:00 2001
> From: Thomas Ackermann <th.acker@arcor.de>
> Date: Sat, 29 Sep 2012 17:28:54 +0200
> Subject: [PATCH] Prerequisites for creating nice html for all files in
>  Documentation/howto
These four lines are not needed; please remove them from all the patches.
Show 20 quoted lines
> @@ -149,13 +152,13 @@ then
>  
>        info "Found matching head pattern: '$head_pattern'"
>        for group_pattern in $group_patterns; do
> -	for groupname in $groups; do
> -	  info "Checking group: '$groupname' against pattern: '$group_pattern'"
> -	  matchlen=$(expr "$groupname" : "$group_pattern")
> -	  if test "$matchlen" = "${#groupname}"
> -	  then
> -	    grant "Allowing group: '$groupname' with pattern: '$group_pattern'"
> -	  fi
> +	    for groupname in $groups; do
> +	      info "Checking group: '$groupname' against pattern: '$group_pattern'"
> +	      matchlen=$(expr "$groupname" : "$group_pattern")
> +	      if test "$matchlen" = "${#groupname}"
> +	      then
> +	        grant "Allowing group: '$groupname' with pattern: '$group_pattern'"
> +	      fi
>          done
>        done

The inner "done" does not seem to align with the "for ...; do" it corresponds to, does it?

Previous: Thomas AckermannNext: Thomas Ackermann
Message 8 of 12 in “Create single PDF for all HTML files”
  1. 0/8 Create single PDF for all HTML filesThomas Ackermann, Oct 11, 2012
  2. 1/8 Split over-long synopsis in git-fetch-pack.txt into several linesThomas Ackermann, Oct 11, 2012
  3. 2/8 Shorten two over-long lines in git-bisect-lk2009.txt by removing some white-spaceThomas Ackermann, Oct 11, 2012
  4. Junio C HamanoOct 11, 2012
  5. 3/8 Change headline of technical/send-pack-pipeline.txt to not confuse its content with content from git-send-pack.txtThomas Ackermann, Oct 11, 2012
  6. 4/8 Prerequisites for creating nice html for all files in Documentation/technicalThomas Ackermann, Oct 11, 2012
  7. 5/8 Prerequisites for creating nice html for all files in Documentation/howtoThomas Ackermann, Oct 11, 2012
  8. Junio C HamanoOct 11, 2012
  9. 6/8 Prerequisites for creating nice html for all files in Documentation/RelNotesThomas Ackermann, Oct 11, 2012
  10. 7/8 Create pdf from all html filesThomas Ackermann, Oct 11, 2012
  11. 8/8 Wire everything into Makefile and Documentation/MakefileThomas Ackermann, Oct 11, 2012
  12. Junio C HamanoOct 11, 2012

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.