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

Re: [PATCH] gitweb: Show project README if available

From
LTLuben Tuikov <ltuikov@yahoo.com>
Date
Oct 10, 2006, 05:15 UTC
Message-ID
<20061010051545.15859.qmail@web31801.mail.mud.yahoo.com>
In-Reply-To
<20061010025627.19317.70511.stgit@rover>
--- Petr Baudis <pasky@suse.cz> wrote:
Show 8 quoted lines
> If the project includes a README file, show it in the summary page.
> The usual "this should be in the config file" argument does not apply here
> since this can be larger and having such a big string in the config file
> would be impractical.
> 
> I don't know if this is suitable upstream, but it's one of the repo.or.cz
> custom modifications that I've thought could be interesting for others
> as well.
I don't see how a read-me file relates to gitweb.

People may call those files "00README" or "README.txt" or "README.TXT" or "README_001", etc.

The contents of such a file has nothing to do with gitweb, and or git. It may work for repo.or.cz but is unlikely that it would work for all projects for all git repos and for all gitweb interfaces.

The contents of a read-me file could be quite large and thus not suitable for the "summary" page. Both the contents and the size may not be suitable. "repo.or.cz" is the exception, not the rule.

A readme file isn't written with the intent of git or gitweb. It is a function of the project, not the SCM used to keep it in, or the SCM web interface used to show it.

I don't understand why the "description" file doesn't do what you want? Do you need it to be multi-line or slightly larger? Why not just extend "description" and/or create/use a second file called "description_long" to store multi-line descriptions?

Or why not extend the "description" file s.t. only the first line would be shown in the "description" line of "summary" and down below, show the rest of the description file if present?

This way it is known that this is a function of gitweb.
     Luben
Show 31 quoted lines
> 
> Signed-off-by: Petr Baudis <pasky@suse.cz>
> ---
> 
>  gitweb/gitweb.perl |    8 ++++++++
>  1 files changed, 8 insertions(+), 0 deletions(-)
> 
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index 7547c4d..4e56af9 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -2535,6 +2535,14 @@ sub git_summary {
>  	}
>  	print "</table>\n";
>  
> +	if (-s "$projectroot/$project/README") {
> +		if (open my $fd, "$projectroot/$project/README") {
> +			print "<div class=\"title\">readme</div>\n";
> +			print $_ while (<$fd>);
> +			close $fd;
> +		}
> +	}
> +
>  	open my $fd, "-|", git_cmd(), "rev-list", "--max-count=17",
>  		git_get_head_hash($project)
>  		or die_error(undef, "Open git-rev-list failed");
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
Previous: Jakub NarebskiNext: Andreas Ericsson
Message 6 of 14 in “gitweb: Show project README if available”
  1. gitweb: Show project README if availablePetr Baudis, Oct 10, 2006
  2. Junio C HamanoOct 10, 2006
  3. Junio C HamanoOct 10, 2006
  4. Petr BaudisOct 10, 2006
  5. Jakub NarebskiOct 10, 2006
  6. Luben TuikovOct 10, 2006
  7. Andreas EricssonOct 10, 2006
  8. Jakub NarebskiOct 10, 2006
  9. Petr BaudisOct 10, 2006
  10. Jakub NarebskiOct 11, 2006
  11. Jeff KingOct 11, 2006
  12. Jakub NarebskiOct 11, 2006
  13. Junio C HamanoOct 11, 2006
  14. Jakub NarebskiOct 11, 2006

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.