From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Bernhard R. Link" <brl+git@mail.brlink.eu>
Subject: Re: What's cooking in git.git (Jan 2012, #08; Tue, 31)
Date: Wed, 01 Feb 2012 04:07:14 -0800 (PST) [thread overview]
Message-ID: <m3fweudaf6.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vlion3tr5.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> --------------------------------------------------
> [Cooking]
>
> * bl/gitweb-project-filter (2012-01-31) 8 commits
> - gitweb: Make project search respect project_filter
> - gitweb: improve usability of projects search form
> - gitweb: place links to parent directories in page header
> - gitweb: show active project_filter in project_list page header
> - gitweb: limit links to alternate forms of project_list to active project_filter
> - gitweb: add project_filter to limit project list to a subdirectory
> - gitweb: prepare git_get_projects_list for use outside 'forks'.
> - gitweb: move hard coded .git suffix out of git_get_projects_list
>
> Seems to break test 9502.
Hmmm... strange. I have applied my patches on top of earlier version
of project_filter commits:
- gitweb: Make project search respect project_filter
- gitweb: Improve projects search form
- gitweb: place links to parent directories in page header
- gitweb: add project_filter to limit project list to a subdirectory
and all gitweb tests passes.
I will investigate.
--
Jakub Narebski
next prev parent reply other threads:[~2012-02-01 12:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 7:19 What's cooking in git.git (Jan 2012, #08; Tue, 31) Junio C Hamano
2012-02-01 12:07 ` Jakub Narebski [this message]
2012-02-01 20:37 ` Junio C Hamano
2012-02-01 20:46 ` Junio C Hamano
2012-02-02 4:21 ` Junio C Hamano
2012-02-10 2:27 ` Junio C Hamano
2012-02-10 4:09 ` Junio C Hamano
2012-02-10 4:43 ` Nguyen Thai Ngoc Duy
2012-02-10 5:48 ` Junio C Hamano
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=m3fweudaf6.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=brl+git@mail.brlink.eu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.