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

[PATCH] gitweb: 'pickaxe' feature requires 'search' enabled

From
Jakub Narebski <jnareb@gmail.com>
Date
Jun 20, 2011, 21:40 UTC
Message-ID
<20110620213904.11650.60345.stgit@localhost.localdomain>
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
This is something I noticed when working on improving gitweb search.
 gitweb/gitweb.perl |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index c9e6426..1a59781 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -342,6 +342,7 @@ our %feature = (
 	# Enable the pickaxe search, which will list the commits that modified
 	# a given string in a file. This can be practical and quite faster
 	# alternative to 'blame', but still potentially CPU-intensive.
+	# Note that you need to have 'search' feature enabled too.
 
 	# To enable system wide have in $GITWEB_CONFIG
 	# $feature{'pickaxe'}{'default'} = [1];
Next: Jakub Narebski
Message 1 of 2 in “gitweb: 'pickaxe' feature requires 'search' enabled”
  1. gitweb: 'pickaxe' feature requires 'search' enabledJakub Narebski, Jun 20, 2011
  2. gitweb: 'pickaxe' and 'grep' features requires 'search' to be enabledJakub Narebski, Jun 21, 2011

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.