From: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Jakub Narebski <jnareb@gmail.com>, Git List <git@vger.kernel.org>,
Petr Baudis <pasky@ucw.cz>
Subject: Re: [PATCHv3 GSoC] gitweb: Move static files into seperate subdirectory
Date: Fri, 14 May 2010 21:45:35 +0530 [thread overview]
Message-ID: <AANLkTimlfiIulCUGf9WHMU2f4wlR3in83VR9UkP0-vi6@mail.gmail.com> (raw)
In-Reply-To: <4BEBC001.10803@gmail.com>
Jakub, I would like to know the status of this patch.
On Thu, May 13, 2010 at 2:31 PM, Pavan Kumar Sunkara
<pavan.sss1991@gmail.com> wrote:
>
>>> First you have to generate gitweb.cgi from gitweb.perl using
>>> -"make gitweb", then copy appropriate files (gitweb.cgi, gitweb.js,
>>> -gitweb.css, git-logo.png and git-favicon.png) to their destination.
>>> -For example if git was (or is) installed with /usr prefix, you can do
>>> +"make gitweb", then "make install-gitweb" appropriate files
>>>
>
> Sorry about that.
>
> - Pavan
>
next prev parent reply other threads:[~2010-05-14 16:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 13:56 [Patch 001/GSoC] Move static files into subdir Pavan Kumar Sunkara
2010-05-09 17:10 ` Christian Couder
2010-05-09 17:48 ` Pavan Kumar Sunkara
2010-05-09 22:13 ` Jakub Narebski
2010-05-10 11:44 ` Pavan Kumar Sunkara
2010-05-10 11:53 ` Ramkumar Ramachandra
2010-05-10 12:55 ` [PATCHv2 GSoC] gitweb: Move static files into seperate subdirectory Jakub Narebski
2010-05-10 13:01 ` Pavan Kumar Sunkara
2010-05-11 23:27 ` Jakub Narebski
2010-05-12 5:15 ` Pavan Kumar Sunkara
2010-05-12 7:52 ` [PATCHv3 " Pavan Kumar Sunkara
2010-05-13 8:54 ` Christian Couder
2010-05-13 9:01 ` Pavan Kumar Sunkara
2010-05-14 16:15 ` Pavan Kumar Sunkara [this message]
2010-05-14 21:25 ` Jakub Narebski
2010-05-15 8:47 ` Pavan Kumar Sunkara
2010-05-18 0:06 ` 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=AANLkTimlfiIulCUGf9WHMU2f4wlR3in83VR9UkP0-vi6@mail.gmail.com \
--to=pavan.sss1991@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=pasky@ucw.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).