git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Git List <git@vger.kernel.org>,
	Christian Couder <chriscool@tuxfamily.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [GSoC update] Splitting gitweb & developing write functionalities
Date: Wed, 16 Jun 2010 02:43:57 +0530	[thread overview]
Message-ID: <AANLkTimJqFzuWI7EMnUuH9ap69KgL_op_yndWSfyg8hX@mail.gmail.com> (raw)
In-Reply-To: <20100615205755.GJ3109@machine.or.cz>

On Wed, Jun 16, 2010 at 2:27 AM, Petr Baudis <pasky@suse.cz> wrote:
>  Hi!
>
> On Wed, Jun 16, 2010 at 02:03:50AM +0530, Pavan Kumar Sunkara wrote:
>> >> gitweb: Create Gitweb::View module [Work in Progress]
>> >
>> > (Is this the Gitweb::HTML module? Why have you renamed it?)
>> Yeah I thought it would be better if I have this named as View rather
>> than HTML :)
>
>  I'm just a bit surprised since I have thought we have agreed that
> Gitweb::View is much more misleading name for what Gitweb::HTML actually
> is, hinting at a MVC structure that simply is not there at any level.
> You are welcome to differ in opinion but then I would expect you to
> continue that discussion. :-)
>

Yes but after a long thought, I decided that the name to be changed to
View because this module contains all the subroutines regarding the
gitweb viewing functions.

Thanks,
Pavan.

  reply	other threads:[~2010-06-15 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 20:03 [GSoC update] Splitting gitweb & developing write functionalities Pavan Kumar Sunkara
2010-06-15 20:17 ` Petr Baudis
2010-06-15 20:33   ` Pavan Kumar Sunkara
2010-06-15 20:57     ` Petr Baudis
2010-06-15 21:13       ` Pavan Kumar Sunkara [this message]
2010-06-16  7:30         ` Petr Baudis
2010-06-18 20:33           ` 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=AANLkTimJqFzuWI7EMnUuH9ap69KgL_op_yndWSfyg8hX@mail.gmail.com \
    --to=pavan.sss1991@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pasky@suse.cz \
    /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).