From: Jakub Narebski <jnareb@gmail.com>
To: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Cc: Christian Couder <chriscool@tuxfamily.org>,
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 23:25:03 +0200 [thread overview]
Message-ID: <201005142325.04747.jnareb@gmail.com> (raw)
In-Reply-To: <AANLkTimlfiIulCUGf9WHMU2f4wlR3in83VR9UkP0-vi6@mail.gmail.com>
On Fri, 14 May 2010, Pavan Kumar Sunkara wrote:
> Jakub, I would like to know the status of this patch.
I like it, and I think all issues (especially with regard to git-instaweb)
got addressed, but the patch itself is heavily whitespace damaged. Could
you please then resend it as attachement (of *.txt file to have text/plain),
if you are not able to send it inline without whitespace munging? Thanks
in advance.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-05-14 21:25 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
2010-05-14 21:25 ` Jakub Narebski [this message]
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=201005142325.04747.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.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).