Skip to content

Commit

Permalink
gitweb: 'pickaxe' and 'grep' features requires 'search' to be enabled
Browse files Browse the repository at this point in the history
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 <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
Jakub Narebski authored and Junio C Hamano committed Jun 21, 2011
1 parent daab4ee commit a598ded
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions gitweb/gitweb.perl
Original file line number Diff line number Diff line change
Expand Up @@ -320,6 +320,7 @@ sub evaluate_uri {
# Enable grep search, which will list the files in currently selected
# tree containing the given string. Enabled by default. This can be
# potentially CPU-intensive, of course.
# Note that you need to have 'search' feature enabled too.

# To enable system wide have in $GITWEB_CONFIG
# $feature{'grep'}{'default'} = [1];
Expand All @@ -334,6 +335,7 @@ sub evaluate_uri {
# 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];
Expand Down

0 comments on commit a598ded

Please sign in to comment.