All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sensors.conf manpage name
Date: Wed, 30 Sep 2009 08:10:33 +0000	[thread overview]
Message-ID: <4AC31279.1020106@redhat.com> (raw)
In-Reply-To: <4AC1C369.8090901@redhat.com>

Hi,

On 09/29/2009 02:57 PM, Jean Delvare wrote:
> Hi Hans,
>
> On Tue, 29 Sep 2009 10:20:57 +0200, Hans de Goede wrote:
>> I just received this bug report:
>> https://bugzilla.redhat.com/show_bug.cgi?idR6178
>>
>> Which makes sense, so now I was thinking how to best handle this. We
>> can make a sensors3.conf.5 symlink to sensors.conf.5 or we can just
>> rename it. There is something to be said for both cases.
>>
>> sensors3.conf is the new default name, but sensors.conf is still used
>> as a fallback by libsensors.
>>
>> So what is your 2 cents on this ?
>
> I believe a symlink would solve the problem better. If we rename the
> man page, then I can see old-timers complain next time they try "man
> sensors.conf" and it fails. And as you said, both names are equally
> valid.
>

Ok, so a symlink it is. Hmm:

[hans@localhost trunk]$ svn update
svn: OPTIONS of 'http://lm-sensors.org/svn/lm-sensors/trunk': could not connect to server (http://lm-sensors.org)
[hans@localhost trunk]$

Am I doing something wrong, or ?

Regards,

Hans

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2009-09-30  8:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29  8:20 [lm-sensors] sensors.conf manpage name Hans de Goede
2009-09-29 12:57 ` Jean Delvare
2009-09-30  8:10 ` Hans de Goede [this message]
2009-09-30  8:12 ` Jean Delvare
2009-10-01  7:01 ` Axel Thimm
2009-10-01  7:03 ` Jean Delvare
2009-10-01  7:30 ` Hans de Goede

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=4AC31279.1020106@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=lm-sensors@vger.kernel.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.