All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: import queue(3) man page ?
Date: Tue, 04 Nov 2008 11:07:47 -0500	[thread overview]
Message-ID: <49107353.2010906@gmail.com> (raw)
In-Reply-To: <200810260500.39607.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>

Mike,

Mike Frysinger wrote:
> On Sunday 26 October 2008, Christoph Hellwig wrote:
>> On Sun, Oct 26, 2008 at 04:22:46AM -0400, Mike Frysinger wrote:
>>> it's the "updated" part that's the rub.  stock glibc has an ancient
>>> queue.h while we've been updating it in Gentoo.  i thought i checked and
>>> found that man-pages simply didnt have one, but it's more a matter of it
>>> being old.
>> When I imported queue.h it matches what was in glibc back then.  I tried
>> updating queue.h in glibc around the same time, but Uli doesn't like it.
> 
> yeah, it should get updated or punted already.
> 
>> Updating the man page to reflected some distro fork of the header
>> doesn't seem like a good idea.
> 
> i wasnt suggesting we do that.  i was explaining why i started this thread in 
> the first place.
> 
>> And at least five year ago all the maintained BSDs actually had quite
>> different additions to queue.h, so which one to pick would be rather
>> hard and I at least partially understand Uli's rejection.
> 
> meh, having an outdated one is just as bad i think.

Are there some specific pieces you can see that need fixing in the
upstream page?  If so, would you have the time to write a patch?

thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
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:[~2008-11-04 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26  4:58 import queue(3) man page ? Mike Frysinger
     [not found] ` <200810260058.02527.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2008-10-26  8:13   ` Christoph Hellwig
     [not found]     ` <20081026081335.GA20872-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2008-10-26  8:22       ` Mike Frysinger
     [not found]         ` <200810260422.47918.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2008-10-26  8:30           ` Christoph Hellwig
     [not found]             ` <20081026083055.GA9020-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2008-10-26  9:00               ` Mike Frysinger
     [not found]                 ` <200810260500.39607.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2008-11-04 16:07                   ` Michael Kerrisk [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=49107353.2010906@gmail.com \
    --to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vapier-aBrp7R+bbdUdnm+yROfE0A@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 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.