search for: formalise

...blic) responsibility so that new contributors know who to talk to, but also to make it clear that if you are no longer up to the task you step down from it. (Currently this often is fuzzy, people may have a different notion about their responsibility than what other think ?) - It formalises tasks and responsibilities - Reward the people that have a responsibility Now, along with that index page, it would be nice if we could also create a good template for every individual with the following (optional) items: - Name - Contact information - Interests - Person list of achi...

...ames.txt as the "Recording Document" for variable names, thus giving it the authority of the RFC. It would be useful to clarify this in the introductory paragraph beginning "This is a dump...". It is more than a dump. The process for adding a variable name to NUT could be formalised under a new heading such as "Process for adding new variable names". The text following that heading could then introduce experimental.... variables. Roger

...ames.txt as the "Recording Document" for variable names, thus giving it the authority of the RFC. It would be useful to clarify this in the introductory paragraph beginning "This is a dump...". It is more than a dump. The process for adding a variable name to NUT could be formalised under a new heading such as "Process for adding new variable names". The text following that heading could then introduce experimental.... variables. Roger

Good morning, I am Martin Bodin, a postdoc at the CMM in Santiago de Chile, and I am currently in the process of formalising (a part of) the R language into the Coq proof assistant. This work makes me look frequently at the source code of R. I have noticed a strange line in the file src/main/util.c of the trunk branch:

# Automatically generated email from bts, devscripts version 2.10.35 # via tagpending # # logcheck (1.3) unstable; urgency=low # # * Formalise the dropping of violations.d/logcheck. Please see # /usr/share/doc/logcheck-database/NEWS.Debian.gz for more information # (closes: #471072). # * Add Auto-Submitted header to outgoing mails (closes: #489172). # * ignore.d.server/kernel: # - ignore unsupported function warnings from PnPBI...

Thanks very much for the quick response. I have read the text many times, but it was not very clear to me why checking the two conditions involving dominance frontiers is equivalent to proving the pair {entry, exit} defines a refined region. I was asking for an mathematical proof really. It sounds to me like there should be a theorem or two in the graph theory endorsing it. Or do you mean, the

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!

...was considered "my" proposal was actually not what I would have wanted or benefited me. But we do have limited time to discuss (and work on the compiler at the same time), and I don't want to drag this for years (I don't have the stamina). So, the current "plan" is to formalise all proposals in around a month's time by uploading them as documents to docs/Proposals/*.rst, then put the survey up and let people take their time to answer (another month), than take some time to analyse the results, sharing the results with the community. If all goes well, we can do a sessi...

I agree with Paul that we need to formalise the compatibility policy before we start removing support for old intrinsics. Do we want a deprecation warning of some kind for the use of any intrinsic used in auto-upgrade, would that actually be useful or just a nuisance? In the meantime I’m happy to help fix any missing test coverage. > On...

...decide to uprev the version we support). Unfortunately, the testing was only added around 3.6 or 3.7? And support is only as good as the testing we have... -- Mehdi 2017-09-21 0:23 GMT-07:00 Simon Pilgrim via llvm-dev < llvm-dev at lists.llvm.org>: > I agree with Paul that we need to formalise the compatibility policy > before we start removing support for old intrinsics. Do we want a > deprecation warning of some kind for the use of any intrinsic used in > auto-upgrade, would that actually be useful or just a nuisance? > > In the meantime I’m happy to help fix any missing...

> On Oct 19, 2015, at 9:27 AM, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Mon, Oct 19, 2015 at 08:25:16AM -0700, Chris Lattner via llvm-dev wrote: >> 1) We could introduce a novel legal solution. > > Please, no. > >> 2) We could require new contributors to sign the Apache CLA. > > To me, this is the most acceptable

...t;Recording Document" > for variable names, thus giving it the authority of the RFC. It would be > useful to clarify this in the introductory paragraph beginning "This is a > dump...". It is more than a dump. The process for adding a variable name to > NUT could be formalised under a new heading such as "Process for adding new > variable names". > The text following that heading could then introduce experimental.... > variables. I suggest replacing the first paragraph of the file nut-names.txt with the something like the following:...

...t;Recording Document" > for variable names, thus giving it the authority of the RFC. It would be > useful to clarify this in the introductory paragraph beginning "This is a > dump...". It is more than a dump. The process for adding a variable name to > NUT could be formalised under a new heading such as "Process for adding new > variable names". > The text following that heading could then introduce experimental.... > variables. I suggest replacing the first paragraph of the file nut-names.txt with the something like the following:...

As can be seen in the trunk, I'm working on the alarm functions in NUT. Only two drivers actively use these at the moment and I intend to add a third one to that (usbhid-ups, in an effort to clean up the mess we created there with undocumented status flags). At the moment, docs/new-drivers.txt says about the alarm functions the following: "There is no official list of alarm words as of

Hi all, I have an idea for a proposal for the summer of code which I think is pretty cool, but I wanted to run it past you all to see what you thought of it first. Basically, the proposal is to use LLVM as a test bed for a more theoretical idea I have. I want to develop a grammar-level way of formally specifying how to translate between two languages. Borrowing from XSLT (a way of transforming

Hello all, 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 During discussions of these contributions, original driver authors often

Hello all, 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 During discussions of these contributions, original driver authors often

I wonder if it isn't time to change the reply-to-list policy of R-help and adopt the alternative convention of replying to the author and asking him/her to summarize to the list. Recently R-help has been too busy for me to keep up with. There were quite a few identical responses in the "Finding indices with a certain property" thread, rather than an extended discussion. I think

hi all, i've searched the samba archived but found little information on the topic related to setting permissions. i wanted to have this effect on a share -- SHARE: [answers] | +--- 1 ---+-- date1 | | | +-- date2 | +--- 2 ---+-- date1 | +-- date2 GROUPS: faculty, students PATH: /home/samba/shares/answers ../answers/ (faculty

...erall aim here is to be openly inclusive to extend the baseline platform that CentOS Linux can run on. In the coming days, we will organise an inaugural meeting on irc, and invite interested people to come help form the initial bootstrap admin group for the SIG. This initial meeting will also help formalise some of the work that has been happening around the edges already in the Aarch64, ARMv7, PowerPC and i686 platforms around CentOS Linux 7. If you are interested in being a part of this, for any of these architectures ( or others! ), get in touch with me. enjoy! - -- Karanbir Singh, Project Lead,...