Subject: Re: What's cooking in git.git (Jul 2015, #05; Mon, 20)

From: Jakub Narębski <[email-masked]>
Date: Tue, 21 Jul 2015 20:56:46 +0200

On 2015-07-21, Junio C Hamano wrote:

> --------------------------------------------------
> [Stalled]
> 
> * sg/config-name-only (2015-05-28) 3 commits
>  - completion: use new 'git config' options to reliably list variable names
>  - SQUASH
>  - config: add options to list only variable names
> 
>  "git config --list" output was hard to parse when values consist of
>  multiple lines.  Introduce a way to show only the keys.

Errr... isn't it what we have -z / --null for?

>  Adding a single --name-only option may be a better way to go than
>  adding two new options.

But that is a good idea anyway.

> * tf/gitweb-project-listing (2015-03-19) 5 commits
>  - gitweb: make category headings into links when they are directories
>  - gitweb: optionally set project category from its pathname
>  - gitweb: add a link under the search box to clear a project filter
>  - gitweb: if the PATH_INFO is incomplete, use it as a project_filter
>  - gitweb: fix typo in man page
> 
>  Update gitweb to make it more pleasant to deal with a hierarchical
>  forest of repositories.
> 
>  Any comments from those who use or have their own code in Gitweb?

Sent a reply to wrong (old) thread, sorry.

tl;dr - first can be applied unconditionally, others have slight
issues. Cgit implements something like this, though with limit
(only first directory path), and different UI - it looks useful
on https://git.kernel.org/cgit/
 
-- 
Jakub Narębski