From: Sebastien Cevey <seb@cine7.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2009, #04; Sun, 15)
Date: Mon, 16 Feb 2009 16:27:22 +0100 [thread overview]
Message-ID: <1234798042.499985da2915e@mail.nimag.net> (raw)
In-Reply-To: <m3ocx4t0mv.fsf@localhost.localdomain>
Selon Jakub Narebski <jnareb@gmail.com>:
Hello Jakub,
> Junio C Hamano <gitster@pobox.com> writes:
>
> > * 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
> >
> > Design discussion between Jakub and Sebastien seems to have stalled.
>
> But I am bit stalled at second patch in the series, which extract
> _printing_ the rows in separate function... while it should IMHO also
> refactor _filtering_ projects list, and not have "filtering as we
> print" current code uses... which would be night incompatibile with
> dividing projects list into pages.
>
> I think this patch series is definitely for after 1.6.2
Okay, I am sorry but I'm going to give up at this point. This patch has been in
the pipeline since July 27, 2008. I understand the iterative review process to
ensure a certain code quality and acknowledge that these patches weren't
perfect
(and probably still aren't), but it's a bit too much of extra rewrite to
support
features that didn't exist and still don't exist yet AFAIK (page splitting of
projects page?). Feel free to take over and do the changes you have in mind,
it'd probably be faster than trying to guide me through it; I still believe
it'd
be a welcome feature, and we've been waiting for it to be merged upstream for
quite a while to activate it on the XMMS2 gitweb.
I have to admit I'm not particularly fond of hacking Perl, but the effort to
get
this rather simple and isolated feature merged don't make it very attractive.
It's a single 6300+ line Perl script we're talking about after all.
Regards,
--
Sebastien Cevey - inso.cc
next prev parent reply other threads:[~2009-02-16 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 10:40 What's cooking in git.git (Feb 2009, #04; Sun, 15) Junio C Hamano
2009-02-15 11:12 ` Jakub Narebski
2009-02-16 15:27 ` Sebastien Cevey [this message]
2009-02-16 16:44 ` Jakub Narebski
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=1234798042.499985da2915e@mail.nimag.net \
--to=seb@cine7.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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;
as well as URLs for NNTP newsgroup(s).