git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2011, #02; Mon, 8)
Date: Thu, 11 Aug 2011 09:30:56 +0200	[thread overview]
Message-ID: <201108110930.57316.jnareb@gmail.com> (raw)
In-Reply-To: <7vk4alrmjd.fsf@alter.siamese.dyndns.org>

On Wed, 10 Aug 2011, Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> --------------------------------------------------
>>> [Graduated to "master"]
>>
>>> * jn/gitweb-config-list-case (2011-07-31) 1 commit
>>>   (merged to 'next' on 2011-08-01 at 9268738)
>>>  + gitweb: Git config keys are case insensitive, make config search too
>>> 
>>> * jn/gitweb-system-config (2011-07-24) 1 commit
>>>   (merged to 'next' on 2011-08-01 at 4941e45)
>>>  + gitweb: Introduce common system-wide settings for convenience
>>
>> What happened with "[PATCH/RFC 0/6] gitweb: Improve project search"
>> series from 29.07.2011?
> 
> I dunno--you tell me ;-)
> 
> You solicited for comments, presumably you collected them and have been
> preparing a re-roll based on the comments? Or perhaps nobody was
> interested in these changes and you dropped it?

I did not get any responses, unfortunately.

The interest in gitweb patches waxes and wanes, and it looks like it is
time for waning interest.  It is a bit frustrating that there is no
response even from people who use gitweb for web interface to hosting
git repositories... but perhaps it is bad time of year.

Anyway, I plan on re-rolling search improvement series, checking if
search is covered by testsuite (IIRC it is).

-- 
Jakub Narebski
Poland

      reply	other threads:[~2011-08-11  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 22:59 What's cooking in git.git (Aug 2011, #02; Mon, 8) Junio C Hamano
2011-08-09  5:36 ` Ramkumar Ramachandra
2011-08-10 11:48 ` Jakub Narebski
2011-08-10 21:20   ` Junio C Hamano
2011-08-11  7:30     ` Jakub Narebski [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=201108110930.57316.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).