From: Jakub Narebski <jnareb@gmail.com>
To: Mark Rada <marada@uwaterloo.ca>
Cc: Charles Bailey <charles@hashpling.org>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCHv5 2/6] Gitweb: add support for minifying gitweb.css
Date: Wed, 14 Apr 2010 22:04:56 +0200 [thread overview]
Message-ID: <201004142204.57323.jnareb@gmail.com> (raw)
In-Reply-To: <4BC614D8.2000208@mailservices.uwaterloo.ca>
On Wed, 14 April 2010, Mark Rada wrote:
> On 10-04-14 1:22 PM, Jakub Narebski wrote:
> > For git-instaweb I think that best solution would be to introduce new
> > variables holding _source_ of gitweb JavaScript code and CSS, e.g.
> >
> > -e '/@@GITWEB_CSS@@/r $(GITWEB_CSS)' \
> >
> > in place of
> >
> > -e '/@@GITWEB_CSS@@/r $(GITWEB_CSS_SOURCE)' \
> >
> > ...although GITWEB_CSS might mean something different for Makefile
> > and git-instaweb than for gitweb/Makefile and gitweb itself.
>
> Did you get those lines mixed up? I might be not understanding something
> here.
Ah, I'm sorry, I mixed up those two lines. They should be in reverse
direction:
-e '/@@GITWEB_CSS@@/r $(GITWEB_CSS_SOURCE)' \
in place of
-e '/@@GITWEB_CSS@@/r $(GITWEB_CSS)' \
Actually I'd like to rename @@GITWEB_CSS@@ placeholder etc. in
git-instaweb.sh, as @@GITWEB_CSS@@ in git-instaweb.sh means something
quite different from ++GITWEB_CSS++ in gitweb/gitweb.perl...
>
> I was actually planning something along the lines of
>
> -e '/@@GITWEB_CSS@@/r $(GITWEB_CSS_NAME)' \
> -e 's|@@GITWEB_CSS_NAME@@|$(GITWEB_CSS_NAME)|' \
>
> where I introduce the GITWEB_CSS_NAME variable, to be consistent with the
> token in instaweb. This way we don't touch GITWEB_JS in the top level
> makefile.
Why not:
-e '/@@GITWEB_CSS_SOURCE@@/r $(GITWEB_CSS_SOURCE)' \
-e '/@@GITWEB_CSS_SOURCE@@/d' \
...
-e 's|@@GITWEB_CSS_NAME@@|$(GITWEB_CSS)|' \
(assuming that $(GITWEB_CSS) does not include '|' in it, I guess...
but see below).
>
> Also, I should update dependancies for instaweb, since those were
> forgotten last time around. Just creating a short list of what the fix will
> need for when I get home tonight.
Something like
git-instaweb: git-instaweb.sh gitweb/gitweb.cgi $(GITWEB_CSS_SOURCE) $(GITWEB_JS_SOURCE)
P.S. I have noticed additional complication: git-instaweb really needs
gitweb compiled with *specific* values of GITWEB_CSS and GITWEB_JS,
so that they point to git-instaweb's installed files.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-04-14 20:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 5:36 [PATCHv5 2/6] Gitweb: add support for minifying gitweb.css Mark Rada
2010-04-01 8:51 ` Jakub Narebski
2010-04-13 20:28 ` Charles Bailey
2010-04-13 22:30 ` Jakub Narebski
2010-04-14 5:40 ` Mark Rada
2010-04-14 17:22 ` Jakub Narebski
2010-04-14 19:17 ` Mark Rada
2010-04-14 20:04 ` Jakub Narebski [this message]
2010-04-14 23:58 ` Junio C Hamano
2010-04-15 0:18 ` Charles Bailey
2010-04-15 0:25 ` Jakub Narebski
2010-04-15 0:46 ` Junio C Hamano
2010-04-15 1:02 ` Jakub Narebski
2010-04-15 1:21 ` Mark Rada
2010-04-15 1:42 ` Junio C Hamano
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=201004142204.57323.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marada@uwaterloo.ca \
--cc=normalperson@yhbt.net \
/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).