public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alfie John" <alfie-pV9j36CBp5Q@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch] standards.7: Added more references
Date: Tue, 2 Jun 2009 08:13:07 +1000 (EST)	[thread overview]
Message-ID: <59652.59.167.195.42.1243894387.squirrel@h4c.kr> (raw)
In-Reply-To: <cfd18e0f0906010539w7dc1b0aw2b53901bd32994dd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hey,

> I don't doubt that these are the best currently available books on
> their subject matter, but in the end, I don't think standards(7)
> should act as a bibliography.

> But my inclination would be to take the references to Gallmeister and
> Lewine out (both now rather dated), rather than add more references.
> And in fact, that is what I've done. (Adding more books to
> standards(7) would only lead me into temptation one day in the
> future.)

Are you sure that is the best thing to do? Man pages are there to help the
reader get a better picture. The more information the better I would have
thought.

What if somebody were to look at standards(7) and wanted to know more
information? Instead of going to what people considered the best material
available (be it books, websites etc), they would instead waste their time
searching and maybe getting inferior or incorrect information. This leads
to floods of questions to forums, IRC and mailing lists. And I'm sure one
common response to these type of questions is going to be "if you want
more info, the best place is X book"!

It would cut out the middle man if references were there from the
beginning :)

> So, sorry -- but I won't take this patch.

No problem. I'm just trying to help out people who are in the same boat as
me -- people wanting to know where the best place to find things are.
Maybe a man page called "unix-references", "unix-books" or
"programming-books" would be a better option.

Alfie
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-06-01 22:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 12:03 [patch] standards.7: Added more references Alfie
     [not found] ` <45544.118.208.205.39.1243685024.squirrel-pV9j36CBp5Q@public.gmane.org>
2009-05-31 18:28   ` Andi Kleen
2009-06-01 12:39   ` Michael Kerrisk
     [not found]     ` <cfd18e0f0906010539w7dc1b0aw2b53901bd32994dd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-01 22:13       ` Alfie John [this message]
     [not found]         ` <59652.59.167.195.42.1243894387.squirrel-pV9j36CBp5Q@public.gmane.org>
2009-06-02  4:14           ` Michael Kerrisk
     [not found]             ` <cfd18e0f0906012114l95fdfd3pff241c319335cef4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-02  8:21               ` Alfie John

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=59652.59.167.195.42.1243894387.squirrel@h4c.kr \
    --to=alfie-pv9j36cbp5q@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox