git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Sebastien Cevey <seb@cine7.net>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org,
	Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Subject: Re: What's cooking in git.git (Jan 2009, #02; Sun, 11)
Date: Fri, 23 Jan 2009 13:04:22 +0100	[thread overview]
Message-ID: <200901231304.23977.jnareb@gmail.com> (raw)
In-Reply-To: <1232548106.4977310a95d8f@mail.nimag.net>

On Wed, 21 Jan 09, Sebastien Cevey wrote:

>>>>> ----------------------------------------------------------------
>>>>> [Actively cooking]
>>>>>
>>>>> * sc/gitweb-category (Fri Dec 12 00:45:12 2008 +0100) 3 commits
>>>>>  - gitweb: Optional grouping of projects by category
>>>>>  - gitweb: Split git_project_list_body in two functions
>>>>>  - gitweb: Modularized git_get_project_description to be more generic
>>>>
>>>> This I think needs some further cooking.  I guess with addition of one
>>>> more patch to series categories could be sorted together with projects
>>>> they contain, and not always have to be in fixed ordering.
>>> 
>>> These should be moved to the Stalled category; nobody seems to be
>>> discussing improvements and sending updates to the series as far as I
>>> recall.
>> 
>> I think it is just the author being slow moving; there was quite
>> a bit of time between subsequent versions of this patch series.
> 
> I don't recall what was left to do on top of the series of patches I submitted,
> could you refresh my mind on that if it still needs to be done? I remember the
> discussion trailing off as categorized ordering was being discussed..

I'd have to take a fresh look at discussion but I remember two things:
first, that the code dealing with filtering out projects (e.g. removing
forks) is high incompatibile with introducing later limiting number of
projects per page, as it currently filters out paths _during printing_.
So we might want to have this cleanup before your series (which now
include a bit unnecessary preparation for projects_list view pagination).

Second, there was IMHO one unnecessary sorting, as with one more commit
we can have quite simply categories sorted in order of sorting project
they contain, which means that if we sort projects by age (youngest or
rather most recently changed first) then with one more commit we can
have category containing freshest project first.

I'll try to review this series soon, and if you don't have time I'll
resend them with those minor corrections.
-- 
Jakub Narebski
Poland

  reply	other threads:[~2009-01-23 12:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11  9:51 What's cooking in git.git (Jan 2009, #02; Sun, 11) Junio C Hamano
2009-01-11 12:21 ` Alexander Potashev
2009-01-11 20:24   ` Junio C Hamano
2009-01-11 14:33 ` Jakub Narebski
2009-01-11 22:19   ` Junio C Hamano
2009-01-12  1:25     ` Jakub Narebski
2009-01-12  1:41       ` Junio C Hamano
2009-01-21 14:28       ` Sebastien Cevey
2009-01-23 12:04         ` Jakub Narebski [this message]
2009-01-12  1:58 ` Marcel Koeppen
2009-01-12  4:03   ` 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=200901231304.23977.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=giuseppe.bilotta@gmail.com \
    --cc=seb@cine7.net \
    /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).