similar to: Proposal: "experimental" namespace for non-standard NUT variables

Displaying 20 results from an estimated 30000 matches similar to: "Proposal: "experimental" namespace for non-standard NUT variables"

2021 May 28
2
Proposal: "experimental" namespace for non-standard NUT variables
On Fri, 28 May 2021, Jim Klimov via Nut-upsdev wrote: > ? Looking at NUT pull request (PR) history on GitHub, I see that we have > had a non-trivial number of stalled driver contributions sharing a prominent > similarity: proposed names for some of the variables did not fit into the list > defined at https://github.com/networkupstools/nut/blob/master/docs/nut-names.txt > ? I
2021 May 28
2
Proposal: "experimental" namespace for non-standard NUT variables
On Fri, 28 May 2021, Jim Klimov via Nut-upsdev wrote: > ? Looking at NUT pull request (PR) history on GitHub, I see that we have > had a non-trivial number of stalled driver contributions sharing a prominent > similarity: proposed names for some of the variables did not fit into the list > defined at https://github.com/networkupstools/nut/blob/master/docs/nut-names.txt > ? I
2021 May 28
0
Proposal: "experimental" namespace for non-standard NUT variables
On Fri, 28 May 2021, Roger Price wrote: > On Fri, 28 May 2021, Jim Klimov via Nut-upsdev wrote: > >> ? Looking at NUT pull request (PR) history on GitHub, I see that we have had >> a non-trivial number of stalled driver contributions sharing a prominent >> similarity: proposed names for some of the variables did not fit into the >> list defined at >>
2021 May 28
0
Proposal: "experimental" namespace for non-standard NUT variables
On Fri, 28 May 2021, Roger Price wrote: > On Fri, 28 May 2021, Jim Klimov via Nut-upsdev wrote: > >> ? Looking at NUT pull request (PR) history on GitHub, I see that we have had >> a non-trivial number of stalled driver contributions sharing a prominent >> similarity: proposed names for some of the variables did not fit into the >> list defined at >>
2017 May 24
4
NUT namespace: RFC for new variable addition
On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clepple at gmail.com> wrote: >On May 24, 2017, at 5:11 AM, Arnaud Quette <arnaud.quette at gmail.com> >wrote: >> >> Hi all, >> >> here is another one, related to ATS (automatic transfer switch) this >time. >> >> in order to track "dephasing" between input sources (1 and 2),
2017 May 24
0
NUT namespace: RFC for new variable addition
On May 24, 2017, at 7:56 AM, Jim Klimov <jimklimov at cos.ru> wrote: > > On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clepple at gmail.com> wrote: >> I don't think "dephasing" is common usage, but "phase shift" should >> suffice. >> >> Also, how does this apply to 3-phase systems? Is it nominally 120 >> degrees?
2017 Jun 14
0
NUT namespace: RFC for new variable addition
(hmmm, finally hitting the Sent button...) 2017-05-24 13:56 GMT+02:00 Jim Klimov <jimklimov at cos.ru>: > On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clepple at gmail.com> > wrote: > >On May 24, 2017, at 5:11 AM, Arnaud Quette <arnaud.quette at gmail.com> > >wrote: > >> > >> Hi all, > >> > >> here is another one,
2023 Feb 02
1
A new step in NUT community building - signing up for fiscal hosting!
Hello all, For decades, the NUT project ran without any formal entity or a "money purse" of its own. This proved to be a somewhat limiting factor, since paid services like DNS have to be covered by maintainers (as in ancient times, when city celebrations were paid by randomly elected officials personally), and some other services like hosting for the NUT CI farm have to be solicited
2023 Feb 02
1
A new step in NUT community building - signing up for fiscal hosting!
Hello all, For decades, the NUT project ran without any formal entity or a "money purse" of its own. This proved to be a somewhat limiting factor, since paid services like DNS have to be covered by maintainers (as in ancient times, when city celebrations were paid by randomly elected officials personally), and some other services like hosting for the NUT CI farm have to be solicited
2004 Jul 20
1
Proposal: cache directory tagging convention
Hi rsync'ers, I'm soliciting feedback, discussion, and hopefully eventually support for a (currently very short and simple) proposal that would make it easier and more automatic for users to exclude from backups and other data transfers all the cache directories that various applications create and manage, such as Mozilla's web cache. The idea is simple: if applications that
2008 Feb 28
4
how to uninstall
hello guys i have centos5.1, and my subject is : when i install a package without the rpm tool cause its not rpm package like configure , make , make install how can i uninstall it later ? thank u all for ur time _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE!
2004 Sep 10
0
Non-audio applications
--- Daniel O'Connor <doconnor@gsoft.com.au> wrote: > Hi, > I work for a company which makes meteor and wind radar > (http://www.gsoft.com.au). > > On occasion (ie during meteor showers such as the Leonids) we > configure > the system to save raw data as it comes out of the acquisition > system, > the data rate for this varies (depends on acquisition parameters
2018 Jan 08
0
HEADS UP: Dates for removing components from namespace std::experimental
In the thread titled "RFC: Plan for removing components from namespace std::experimental", (started last April) I put forward a timetable for removing things from libc++ that had become duplicates of other things in libc++. Specifically, things that were in namespace "std::experimental" and "std" both (and subtly different in both). In that RFC, I proposed to let a
2018 Jan 29
0
ONE WEEK until components removed from namespace std::experimental
In the thread titled "RFC: Plan for removing components from namespace std::experimental", (started last April) I put forward a timetable for removing things from libc++ that had become duplicates of other things in libc++. Specifically, things that were in namespace "std::experimental" and "std" both (and subtly different in both). In that RFC, I proposed to let a
2004 Sep 10
3
Non-audio applications
Hi, I work for a company which makes meteor and wind radar (http://www.gsoft.com.au). On occasion (ie during meteor showers such as the Leonids) we configure the system to save raw data as it comes out of the acquisition system, the data rate for this varies (depends on acquisition parameters and number of coherent integrations etc), but usually it is around 600kb/sec. The data consists of 16
2018 Jan 04
0
RFC: Plan for removing components from namespace std::experimental
On Mon, Apr 10, 2017 at 1:22 PM, Marshall Clow <mclow.lists at gmail.com> wrote: > As part of the work on C++17, WG21 released a series of "Technical > Specifications", (TS) which added proposed new features to the standard > library. These were all defined in the namespace 'std::experimental' (and > namespaces inside of that). > > Then, much of these
2007 Dec 13
2
metaflac problem on cygwin
wow, that was a mighty keen eye - you must really have been looking at it (thanx!) - that is just a typo, the example just above and below that line still show that the issue i'm having exists. an easy test anyone can do is: metaflac --version metaflac --show-sample-rate c:/any.flac metaflac --show-sample-rate /cygdrive/c/any.flac On Dec 13, 2007 5:43 PM, Christopher Brown
2020 Nov 13
0
[EXTERNAL] Updates to NUT project leadership
Hello all, I am excited to see the first replies, even if some seem to be private messages. Thank you all! :) In the following case, I think the raised question pertains to many contributors on this list, so would answer publicly - and thanks for asking. > There are various GitHub issues and Dev mailing list inquires, but they haven't really gone anywhere. > Can you provide some
2007 Sep 10
0
Feedback on XML metadata namespace
Silvia Pfeiffer wrote: > Daniel, > > before you step over everything that has been done before, we need to > determine what exactly is the use case for your new specification. > > What concerns metadata, we currently have: > > * vorbiscomment - this is a header at the beginning of a logical > bitstream which has metadata that refers to the complete file; there > is
2023 Apr 07
1
nut server without nut-client/monitor?
Isn't "nut" package there an umbrella/meta-package (in terms of other distros) to pull together the likely suspects in one command? Not at a computer now, but I think Debian and OpenIndiana packages were grouped this way. Likely all packages with daemons would depend on a "nut-common" package then, to consistently deliver user accounts, systemd-tmpfiles and other similar