Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: git/git
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: theefer/git
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 3 commits
  • 3 files changed
  • 1 contributor

Commits on Feb 8, 2009

  1. gitweb: Modularized git_get_project_description to be more generic

    Introduce a git_get_file_or_project_config utility function to
    retrieve a repository variable either from a plain text file in the
    $GIT_DIR or else from 'gitweb.$variable' in the repository config
    (e.g. 'description').
    
    Signed-off-by: Sebastien Cevey <seb@cine7.net>
    theefer committed Feb 8, 2009
    Configuration menu
    Copy the full SHA
    4cc3e46 View commit details
    Browse the repository at this point in the history
  2. gitweb: Split git_project_list_body in two functions

    Extract the printing of project rows on the project page into a
    separate print_project_rows function. This makes it easier to reuse
    the code to print different subsets of the whole project list.
    
    The row printing code is merely moved into a separate function, but
    note that $projects is passed as a reference now.
    
    Signed-off-by: Sebastien Cevey <seb@cine7.net>
    theefer committed Feb 8, 2009
    Configuration menu
    Copy the full SHA
    868a0cf View commit details
    Browse the repository at this point in the history
  3. gitweb: Optional grouping of projects by category

    This adds the $projects_list_group_categories option which, if enabled,
    will result in grouping projects by category on the project list page.
    The category is specified for each project by the $GIT_DIR/category file
    or the 'category' variable in its configuration file. By default, projects
    are put in the $project_list_default_category category.
    
    Note:
    - Categories are always sorted alphabetically, with projects in
      each category sorted according to the globally selected $order.
    - When displaying a subset of all the projects (page limiting), the
      category headers are only displayed for projects present on the page.
    
    The feature is inspired from Sham Chukoury's patch for the XMMS2
    gitweb, but has been rewritten for the current gitweb development
    HEAD. The CSS for categories is inspired from Gustavo Sverzut Barbieri's
    patch to group projects by path.
    
    Thanks to Florian Ragwitz for Perl tips.
    
    Signed-off-by: Sebastien Cevey <seb@cine7.net>
    theefer committed Feb 8, 2009
    Configuration menu
    Copy the full SHA
    f5d949a View commit details
    Browse the repository at this point in the history
Loading