public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org
Subject: Re: where to report i2c-related man page issues?
Date: Mon, 24 Jul 2017 15:05:57 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1707241504510.25387@localhost.localdomain> (raw)
In-Reply-To: <20170724174145.GA1543@katana>

On Mon, 24 Jul 2017, Wolfram Sang wrote:

> On Mon, Jul 24, 2017 at 08:17:34AM -0400, rpjday@crashcourse.ca wrote:
> >
> >   where is the right place to point out current i2c man page issues,
> > or out-of-date passages? thank you kindly.
>
> If you mean i2c-tools, then let me quote the README:
>
> QUESTIONS AND BUG REPORTS
> -------------------------
>
> Please post your questions and bug reports to the linux-i2c mailing list:
>   linux-i2c@vger.kernel.org
> with Cc to the current maintainer:
>   Jean Delvare <jdelvare@suse.de>
> For additional information about this list, see:
>   http://vger.kernel.org/vger-lists.html#linux-i2c

  by the way, the current README file does not include that "Cc" line.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

      parent reply	other threads:[~2017-07-24 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 12:17 where to report i2c-related man page issues? rpjday
2017-07-24 17:41 ` Wolfram Sang
2017-07-24 18:16   ` Robert P. J. Day
2017-07-24 19:05   ` Robert P. J. Day [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=alpine.LFD.2.20.1707241504510.25387@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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