Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: git@vger.kernel.org, Tony Finch <dot@dotat.at>
Subject: Re: What's cooking in git.git (Jul 2015, #05; Mon, 20)
Date: Tue, 21 Jul 2015 12:42:40 -0700	[thread overview]
Message-ID: <xmqq615duwjz.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <55AE95EE.1080500@gmail.com> ("Jakub Narębski"'s message of "Tue, 21 Jul 2015 20:56:46 +0200")

Jakub Narębski <jnareb@gmail.com> writes:

>> * 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/

I'll merge the first one down, and discard the rest without
prejudice, then.

Thanks.

      parent reply	other threads:[~2015-07-21 19:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 23:18 What's cooking in git.git (Jul 2015, #05; Mon, 20) Junio C Hamano
2015-07-21  0:50 ` David Turner
2015-07-21  5:15   ` Junio C Hamano
2015-07-21 16:36     ` David Turner
2015-07-21 18:56 ` Jakub Narębski
2015-07-21 19:41   ` Junio C Hamano
2015-07-21 19:42   ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq615duwjz.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=dot@dotat.at \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox