git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
	git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [RFC/PATCH 1/4] gitweb: Move subroutines to Gitweb::Config module
Date: Tue, 8 Jun 2010 22:50:29 +0200	[thread overview]
Message-ID: <20100608205029.GB3408@machine.or.cz> (raw)
In-Reply-To: <AANLkTimKsdn8Vww_4U4YQDPlpr_BgbVszwG64lEYl-cE@mail.gmail.com>

On Wed, Jun 09, 2010 at 01:54:34AM +0530, Pavan Kumar Sunkara wrote:
> On Wed, Jun 9, 2010 at 1:25 AM, Petr Baudis <pasky@suse.cz> wrote:
> > On Wed, Jun 09, 2010 at 12:52:11AM +0530, Pavan Kumar Sunkara wrote:
> >>   Gitweb::Parse
> >
> > What will this module do?
> 
> This module contains all the parse_* subroutines

Ok, that makes sense. It might be also possible to have them in
Gitweb::Git, but I see href() invocations and such that would probably
create layering violations.

> Gitweb::Format contains all the format_* subroutines

Here, I'm less decided. I would have put these in Gitweb::HTML, but I
have no hard opinion, maybe that's clumping things too much - so no nack
from me personally.

> >>   Gitweb::Util
> >
> > What will this module do?
> 
> This modules contains all the git utility functions.

Can you give an example, please?

> I still have until this week in the timeline. Don't I ?
> I strongly hope that I will be able to finalise the patch queue by
> this week and will move on to develop write functionalities.

Sure, my only concern is that if the queue of patches your future work
will depend on gets too long and gets delayed too much in merging in,
it will get much more difficult to produce further patches, get them
reviewed and get them on the merging track.

-- 
				Petr "Pasky" Baudis
The true meaning of life is to plant a tree under whose shade
you will never sit.

  reply	other threads:[~2010-06-08 20:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 20:50 [RFC/PATCH 1/4] gitweb: Move subroutines to Gitweb::Config module Pavan Kumar Sunkara
2010-06-07 20:50 ` [RFC/PATCH 2/4] gitweb: Create Gitweb::HTML::Link module Pavan Kumar Sunkara
2010-06-07 20:50 ` [RFC/PATCH 3/4] gitweb: Create Gitweb::HTML module Pavan Kumar Sunkara
2010-06-07 20:50 ` [RFC/PATCH 4/4] gitweb: Create Gitweb::HTML::String module Pavan Kumar Sunkara
2010-06-07 20:58   ` Pavan Kumar Sunkara
2010-06-08 12:46 ` [RFC/PATCH 1/4] gitweb: Move subroutines to Gitweb::Config module Jakub Narebski
2010-06-08 13:50   ` Ævar Arnfjörð Bjarmason
2010-06-12  1:01     ` Jakub Narebski
2010-06-12  1:22       ` Ævar Arnfjörð Bjarmason
2010-06-12  1:41         ` Jakub Narebski
2010-06-08 14:13   ` Petr Baudis
2010-06-08 19:22     ` Pavan Kumar Sunkara
2010-06-08 19:55       ` Petr Baudis
2010-06-08 20:24         ` Pavan Kumar Sunkara
2010-06-08 20:50           ` Petr Baudis [this message]
2010-06-08 23:38       ` Jakub Narebski
2010-06-09 13:13         ` 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=20100608205029.GB3408@machine.or.cz \
    --to=pasky@suse.cz \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=pavan.sss1991@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).