Skip to content

Commit a598ded

Browse files
jnarebgitster
authored andcommitted
gitweb: 'pickaxe' and 'grep' features requires 'search' to be enabled
Both 'pickaxe' (searching changes) and 'grep' (searching files) require basic 'search' feature to be enabled to work. Enabling e.g. only 'pickaxe' won't work. Add a comment about this. Signed-off-by: Jakub Narebski <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent daab4ee commit a598ded

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

gitweb/gitweb.perl

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -320,6 +320,7 @@ sub evaluate_uri {
320320
# Enable grep search, which will list the files in currently selected
321321
# tree containing the given string. Enabled by default. This can be
322322
# potentially CPU-intensive, of course.
323+
# Note that you need to have 'search' feature enabled too.
323324

324325
# To enable system wide have in $GITWEB_CONFIG
325326
# $feature{'grep'}{'default'} = [1];
@@ -334,6 +335,7 @@ sub evaluate_uri {
334335
# Enable the pickaxe search, which will list the commits that modified
335336
# a given string in a file. This can be practical and quite faster
336337
# alternative to 'blame', but still potentially CPU-intensive.
338+
# Note that you need to have 'search' feature enabled too.
337339

338340
# To enable system wide have in $GITWEB_CONFIG
339341
# $feature{'pickaxe'}{'default'} = [1];

0 commit comments

Comments
 (0)