git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Sebastien Cevey <seb@cine7.net>,
	Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Subject: Re: What's cooking in git.git (Jan 2009, #02; Sun, 11)
Date: Mon, 12 Jan 2009 02:25:29 +0100	[thread overview]
Message-ID: <200901120225.30175.jnareb@gmail.com> (raw)
In-Reply-To: <7vwsd1pjst.fsf@gitster.siamese.dyndns.org>

On Sun, 11 Jan 2009, Junio C Hamano wrote:
> 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.

I think it is just the author being slow moving; there was quite
a bit of time between subsequent versions of this patch series.
But if Sebastien would not resend this series in about a week,
I'll try to clean it up, add fourth patch, and resend it.

As to lack of discussion: I think it is cause bu two issues. First,
there is support for tags already implemented which somewhat reduces
need for categories support. Second, hosting sites which have large
number of projects for which categories support might be a nice thing,
use I guess modified gitweb with caching, don't they?

>>> * 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'?

Yes, I think so. The changes are cosmetic in nature, and I think
the feature this patch adds is quite useful: you can now get patches
and [short] patch series from gitweb which you can apply using git-am.
Nice, isn't it?

-- 
Jakub Narebski
Poland

  reply	other threads:[~2009-01-12  1:27 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 [this message]
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=200901120225.30175.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.
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).