From: Jakub Narebski <jnareb@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>,
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: Fri, 18 Jun 2010 13:33:37 -0700 (PDT) [thread overview]
Message-ID: <m3wrtwnktb.fsf@localhost.localdomain> (raw)
In-Reply-To: <20100616073017.GK3109@machine.or.cz>
Petr Baudis <pasky@suse.cz> writes:
> On Wed, Jun 16, 2010 at 02:43:57AM +0530, Pavan Kumar Sunkara wrote:
> > 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.
>
> But then you will need to continue the discussion in the respective
> therad and present counter-arguments to our (my?) arguments, or you will
> get NAKs.
>
> (It's not like this is a totally crucial issue, but I'm now rather
> annoyed as what's the point of discussing stuff if it can be all
> discarded at a whim?)
On the other hand gitweb output is not limited to HTML only: it
includes text/plain ("raw" blob aka 'blob_plain' for text files,
'patches' / 'patch', 'projects_index'), feed formats: OPML, RSS, Atom,
and binary output ("raw" blob for binary files like images,
'snapshot').
But I don't know if Gitweb::View includes subroutines related to all
those things.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2010-06-18 20:33 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
2010-06-16 7:30 ` Petr Baudis
2010-06-18 20:33 ` Jakub Narebski [this message]
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=m3wrtwnktb.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
--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).