search for: deliniation

I'm moving from Ubuntu to CentOS 7 Previously, on Ubuntu, installing amavisd would lead to etc/amavis/conf.d that contained: 01-debian 05-domain_id 05-node_id 15-av_scanners 15-content_filter_mode 20-debian_defaults 21-ubuntu_defaults 25-amavis_helpers 30-template_localization 40-policy_banks 50-user However installing amavisd on centos leads to a spaghetti config file (i.e.

On Wed, Jun 13, 2012 at 3:41 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Guys, that was very interesting and useful stuff you preached there. Mind > if I make a patch to the FAQ and include it somewhere? > > "Q: When should I develop against a branch? A: Only if you are making > really big or controversial changes. ... blah blah > > I am thinking that it

I'm forwarding the answer from my colleague: release notes: - provide two new subroutines available for calling from config files: include_config_files() and include_optional_config_files(), each take a list of filenames as arguments, and reads & evaluates them just like normal configuration files specified on a command line (option -c or a default amavisd.conf). This provides a

Hadley, With all due respect, I'm not sure what exactly your deliniation between author and contributor is, but from what I can tell I don't agree with it. >From the blogpost regarding your new purrr package: "Purrr wouldn?t be possible without Lionel Henry <https://github.com/lionel->. He wrote a lot of the package and his insightful comments ...&qu...

> 8. A Technical Writer FAQ (should include the Sphinx documentation from the lld docs). I'm working on the Sphinx stuff; if you have any questions about writing Sphinx docs feel free to ask. --Sean Silva On Wed, Jun 13, 2012 at 4:37 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > I think the best way that I can currently contribute to the project is > through technical

On Tue, Oct 6, 2015 at 4:58 PM, Adrian Du?a <dusa.adrian at unibuc.ro> wrote: > Hi Gabriel, > > On Tue, Oct 6, 2015 at 10:59 PM, Gabriel Becker <gmbecker at ucdavis.edu> > wrote: > >> [...] >> >> At the very least, this is seems to be a flagrant violation of the >> *spirit* of the CRAN policy, which AFAIK is intended to enforce >>

I think the best way that I can currently contribute to the project is through technical writing. So I see myself as doing a serious, long-term project of extending the FAQ. So, I can affirm that I want to really start working :) This at the same time as I plan to regularly release an unofficial Windows distro of Clang with headers and libraries so people don't need to install MinGW to use

I just finished up the first draft of the FAQ translated verbatim from HTML to Sphinx. Sphinx did puzzle me a few times but I got used to its approximate error messages and figured out what the problems were. Perhaps you could take a quick glance at this file and tell me if I am doing something wrong? Otherwise I'll send it off to llvm-commits and see what they say. Thanks, Mikael

Guys, that was very interesting and useful stuff you preached there. Mind if I make a patch to the FAQ and include it somewhere? "Q: When should I develop against a branch? A: Only if you are making really big or controversial changes. ... blah blah I am thinking that it would be highly useful for the project, if somebody (yours sincerely) took it upon himself to hunt and gather the very

...distrTEst, distrTeach, distrMod, and distrEllipse. I haven't checked, but each package could have a separate and different list of authors. Hope this helps. Spencer On 10/7/2015 9:23 AM, Gabriel Becker wrote: > Hadley, > > With all due respect, I'm not sure what exactly your deliniation between > author and contributor is, but from what I can tell I don't agree with it. > > >From the blogpost regarding your new purrr package: > > "Purrr wouldn?t be possible without Lionel Henry > <https://github.com/lionel->. He wrote a lot of the package and hi...

Done. Do you want to see it again or should I simply ship it off to llvm-commits? The only thing I've changed from the original HTML is that I've changed a few missing code pieces into using code markup. And now I've made the changes you requested and I think it looks really good: Each question being a subsection of its own works very well in my opinon. Oh, heck, I might as well

As I read, I'm writing stuff here things come to me: 1. Don't indent the list. Some of the other RST files do this, but it is incorrect since it indents the list! The list is semantically "at the top level" of indentation (it's not a sub-element of anything). 2. don't have that mini "table of contents" list at the beginning. sphinx will generate that itself

On Wed, Jun 13, 2012 at 11:43 AM, Andrew Trick <atrick at apple.com> wrote: > > On Jun 13, 2012, at 7:15 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > Again, this is branch code, but if I can see something wrong in platform > independent portion, I'll track it on the trunk. > > > I hate to be the one to start this thread, but I have to say it at