From: Eli Barzilay <eli@barzilay.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: gitweb.css
Date: Thu, 8 Jul 2010 15:30:39 -0400 [thread overview]
Message-ID: <19510.10079.395353.55808@winooski.ccs.neu.edu> (raw)
In-Reply-To: <201007082125.59544.jnareb@gmail.com>
On Jul 8, Jakub Narebski wrote:
>
> No, what I meant here is that the structure of gitweb page should look
> like the following, in pseudocode: [...]
Ah -- dividing the gitweb content to header/content/footer -- that
makes perfect sense.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
prev parent reply other threads:[~2010-07-08 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 2:43 gitweb.css Eli Barzilay
2010-07-08 16:07 ` gitweb.css Jakub Narebski
2010-07-08 17:42 ` gitweb.css Eli Barzilay
2010-07-08 18:49 ` gitweb.css Jakub Narebski
2010-07-08 18:57 ` gitweb.css Eli Barzilay
2010-07-08 19:25 ` gitweb.css Jakub Narebski
2010-07-08 19:30 ` Eli Barzilay [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=19510.10079.395353.55808@winooski.ccs.neu.edu \
--to=eli@barzilay.org \
--cc=git@vger.kernel.org \
--cc=jnareb@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).