From: Junio C Hamano <gitster@pobox.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2009, #02; Sun, 11)
Date: Sun, 11 Jan 2009 14:19:46 -0800 [thread overview]
Message-ID: <7vwsd1pjst.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: m3ljthzzdq.fsf@localhost.localdomain
Jakub Narebski <jnareb@gmail.com> writes:
>> ----------------------------------------------------------------
>> [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.
>> * gb/gitweb-patch (Thu Dec 18 08:13:19 2008 +0100) 4 commits
>> - gitweb: link to patch(es) view in commit(diff) and (short)log view
>> - gitweb: add patches view
>> - gitweb: change call pattern for git_commitdiff
>> - gitweb: add patch view
>
> If I remember correctly the only point of discussion is calling
> convention for git_commitdiff, and whether 'patches' view should
> (re)use git_commitdiff or use its own subroutine.
Thanks; I take it that it is basically usable, useful and can be
incrementally improved in 'next'?
next prev parent reply other threads:[~2009-01-11 22:21 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 [this message]
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
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vwsd1pjst.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).