Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: ltuikov@yahoo.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb.css: Courer fonts for commits and tree-diff
Date: Tue, 11 Jul 2006 23:02:35 -0700	[thread overview]
Message-ID: <7vac7f1htw.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060712034323.48414.qmail@web31806.mail.mud.yahoo.com> (Luben Tuikov's message of "Tue, 11 Jul 2006 20:43:23 -0700 (PDT)")

Luben Tuikov <ltuikov@yahoo.com> writes:

> Courer fonts for the commit header, commit message,
> and tree-diff.
>
> Signed-off-by: Luben Tuikov <ltuikov@yahoo.com>

I really do not want to be in the position to judge a patch like
this, whose evaluation is solely based on "prettiness" factor.

But if I really have to, I would say this makes things uglier
and less readable.  Maybe asking for monospace is less yucky but
naming Courier explicitly?

BTW what tool do you use to generate and send your patches?  I
remember another patch from you recently did not apply and it
turned out the problem was that the last hunk had line numbers
wrong.  This patch has exactly the same problem and I am
wondering why.

I count 10 lines of original and 15 lines of new material in
this hunk but the hunk header claims to have 11 lines of
original text.

---
 gitweb/gitweb.css |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/gitweb/gitweb.css b/gitweb/gitweb.css
index 98410f5..b51282b 100644
--- a/gitweb/gitweb.css
+++ b/gitweb/gitweb.css
 ... 
@@ -142,11 +144,15 @@ table {
 	padding: 8px 4px;
 }
 
-table.project_list, table.diff_tree {
+table.project_list {
 	border-spacing: 0;
 }
 
+table.diff_tree {
+	border-spacing: 0;
+	font-family: courier;
+}
+
 table.blame {
 	border-collapse: collapse;
 }
-- 
1.4.1.g9ca3

  reply	other threads:[~2006-07-12  6:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  3:43 [PATCH] gitweb.css: Courer fonts for commits and tree-diff Luben Tuikov
2006-07-12  6:02 ` Junio C Hamano [this message]
2006-07-12 17:46   ` Luben Tuikov
2006-07-13  7:57     ` Matthias Lederhofer

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=7vac7f1htw.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=ltuikov@yahoo.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