Displaying 13 results from an estimated 13 matches for "deliniated".
Did you mean:
delineated
2017 Jan 04
2
Amavis on Centosl help
...ant to avoid spaghetti config, not only is it
poor practice, but also nigh on impossible to maintain properly
without breaking stuff.
Assuming it is possible, how would I go about changing the Centos
"dump" based config into a more sensible one where local site
customisations are clearly deliniated ?
2012 Jun 13
3
[LLVMdev] Develop on trunk.
...ries, and
infrastructure in the primary project.
3) A Clang FAQ for the FE-specific stuff.
The current FAQ is mostly #2, with a bit of #1, and a lot of out-of-date or
flat out wrong information. The current FAQ could probably stay as one
page, or be two pages, but it should have a clear and well deliniated split
between #1 and #2. We should discuss creating #3 on cfe-dev in a separate
thread if you're interested.
If you're proposing patches, here are some suggestions as the standard
process may not work as well... which others may contradict if they
disagree... ;]
- Patches to fix the form...
2017 Jan 04
0
Amavis on Centosl help
..., not only is it
> poor practice, but also nigh on impossible to maintain properly
> without breaking stuff.
>
> Assuming it is possible, how would I go about changing the Centos
> "dump" based config into a more sensible one where local site
> customisations are clearly deliniated ?
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
2015 Oct 07
0
authorship and citation
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 ..."
And yet he is
2012 Jun 14
2
[LLVMdev] Develop on trunk.
...t;> 3) A Clang FAQ for the FE-specific stuff.
>>
>>
>> The current FAQ is mostly #2, with a bit of #1, and a lot of out-of-date
>> or flat out wrong information. The current FAQ could probably stay as one
>> page, or be two pages, but it should have a clear and well deliniated split
>> between #1 and #2. We should discuss creating #3 on cfe-dev in a separate
>> thread if you're interested.
>>
>>
>> If you're proposing patches, here are some suggestions as the standard
>> process may not work as well... which others may contradi...
2015 Oct 07
4
authorship and citation
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
>>
2012 Jun 13
0
[LLVMdev] Develop on trunk.
...primary project.
>
> 3) A Clang FAQ for the FE-specific stuff.
>
>
> The current FAQ is mostly #2, with a bit of #1, and a lot of out-of-date
> or flat out wrong information. The current FAQ could probably stay as one
> page, or be two pages, but it should have a clear and well deliniated split
> between #1 and #2. We should discuss creating #3 on cfe-dev in a separate
> thread if you're interested.
>
>
> If you're proposing patches, here are some suggestions as the standard
> process may not work as well... which others may contradict if they
> disagree...
2012 Jun 14
0
[LLVMdev] Develop on trunk.
...Q for the FE-specific stuff.
>>>
>>>
>>> The current FAQ is mostly #2, with a bit of #1, and a lot of out-of-date
>>> or flat out wrong information. The current FAQ could probably stay as one
>>> page, or be two pages, but it should have a clear and well deliniated split
>>> between #1 and #2. We should discuss creating #3 on cfe-dev in a separate
>>> thread if you're interested.
>>>
>>>
>>> If you're proposing patches, here are some suggestions as the standard
>>> process may not work as well... w...
2012 Jun 13
0
[LLVMdev] Develop on trunk.
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
2015 Oct 07
2
authorship and citation
An example from the sos package: Its DESCRIPTION file says Author:
Spencer Graves, Sundar Dorai-Raj, and Romain Francois. However, the
package includes a findFn function, whose help file includes an
Author(s) section, which reads, "Spencer Graves, Sundar Dorai-Raj,
Romain Francois. Duncan Murdoch suggested the "???" alias for "findFn"
and contributed the code for
2012 Jun 14
0
[LLVMdev] Develop on trunk.
...;>>
>>>>> The current FAQ is mostly #2, with a bit of #1, and a lot of
>>>>> out-of-date or flat out wrong information. The current FAQ could probably
>>>>> stay as one page, or be two pages, but it should have a clear and well
>>>>> deliniated split between #1 and #2. We should discuss creating #3 on
>>>>> cfe-dev in a separate thread if you're interested.
>>>>>
>>>>>
>>>>> If you're proposing patches, here are some suggestions as the standard
>>>>> proces...
2012 Jun 14
4
[LLVMdev] Develop on trunk.
...>>
>>>>
>>>> The current FAQ is mostly #2, with a bit of #1, and a lot of
>>>> out-of-date or flat out wrong information. The current FAQ could probably
>>>> stay as one page, or be two pages, but it should have a clear and well
>>>> deliniated split between #1 and #2. We should discuss creating #3 on
>>>> cfe-dev in a separate thread if you're interested.
>>>>
>>>>
>>>> If you're proposing patches, here are some suggestions as the standard
>>>> process may not work as we...
2012 Jun 13
4
[LLVMdev] Develop on trunk.
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