Linux Manual Pages development
 help / color / mirror / Atom feed
From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 84151] right and side → right hand side
Date: Fri, 08 May 2015 09:37:51 +0000	[thread overview]
Message-ID: <bug-84151-11311-5HUV4g97Ch@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-84151-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=84151

--- Comment #5 from Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to Dan Jacobson from comment #4)
> All I am trying to say is that you need a general bug tracker for such
> problems. People will not know that they are supposed to look in various
> files to find various names. And indeed posting to that list often meets
> with no answer. So do consider a Debian-like policy, where one can
> always still post to their bug-tracker, no matter what.

The kernel community is heterogeneous in this respect--some use the bug
tracker, some don't. There is no global (ly enforced) policy. BTSs are of
course not a panacea. I know from my own experience with Debisn that man pages
bug reports sometimes sit there for *years* unattended, sometimes even for
years after I add a note saying the problem is fixed upstream.

The general problem I think is this: Bug Trackers facilitate throwing a problem
to someone else, rather than rolling up your sleeves and getting involved in
the fixing yourself. Yes, we need bug reporters, but the problem is there
aren't enough bug *fixers*. And I think bug reports like this illustrate the
problem quite well. You may say that mails to that list are sometimes ignored,
and I won't disagree, but I think if you sent a well formatted patch to the
list, it'd likely be attended to. For my part, with respect to man-pages, I
explicitly request[1] that people don't use Bugzilla for this kind of report.

Thanks,

Michael

[1] https://www.kernel.org/doc/man-pages/reporting_bugs.html

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
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:[~2015-05-08  9:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  7:04 [Bug 84151] New: right and side → right hand side bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
     [not found] ` <bug-84151-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2015-05-05  5:58   ` [Bug 84151] " bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2015-05-06 23:09   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2015-05-07  4:45   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2015-05-07 14:02   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2015-05-08  9:37   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
2015-05-09 10:16   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r

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=bug-84151-11311-5HUV4g97Ch@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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