All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB webpage
Date: Sun, 8 Aug 2004 02:18:04 +0200	[thread overview]
Message-ID: <200408080218.05357.okuji@enbug.org> (raw)
In-Reply-To: <87smazdlik.fsf@marco.marco-g.com>

On Saturday 07 August 2004 17:18, Marco Gerards wrote:
> If someone has another suggestion to prevent confusion, please tell
> me.  As I know very little about webpages (and because of the lack of
> interest in webpages) all I will do for the GRUB webpage is updating
> the text.
>
> Okuji, can I commit this patch?

No. I don't think it will improve things very much. As I have already 
said (maybe twice), the cause is the structure rather than the text 
itself.

Marco, I'd like to note one thing. AFAIK, no programmer is really 
interested in web pages, especially about the design. Probably this is 
the nature of most programmers, since they are not technically 
interesting. But web pages are still good means of assisting 
development. They reduce the cost of development by directing people to 
right places and they help development itself by attracting more people 
to the project.

Here I don't claim that you should work on web pages, but I claim that 
*someone* must work on them seriously anyway, and I myself don't want 
to work on them very much, like you.

This might sound arrogant, but I really want someone but me for this 
kind of work, because it does not require much knowledge about GRUB and 
I do a lot of legwork for GRUB already.

Okuji



      reply	other threads:[~2004-08-08  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-07 15:18 GRUB webpage Marco Gerards
2004-08-08  0:18 ` Yoshinori K. Okuji [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=200408080218.05357.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.