search for: doctrines

Displaying 20 results from an estimated 60 matches for "doctrines".

Did you mean: doctrine
2015 Feb 11
2
Another Fedora decision
On Tue, 2015-02-10 at 21:32 -0600, Valeri Galtsev wrote: > Indeed I should have said "allegedly pirated" not just "pirated". As I > don't care to go into details if it is or it isn't. I also would recommend > to finish this discussion and those who feel so get themselves some > fundamental book and go ahead with reading it. Which I'm going to do >
2009 Apr 28
3
Inline Link Error?
Hello Everyone, Can someone spot the error in the following snippet of link text? It doesn't work through php-markdown in wordpress and I just wanted to know if there's something obvious I'm missing. Thanks in advance! can come of us. "Every good and perfect gift comes from above" ([James
2015 Feb 11
0
Another Fedora decision
On Tue, Feb 10, 2015 at 8:55 PM, Always Learning <centos at u64.u22.net> wrote: > Before an unnecessary riot starts perhaps I should mention I've borrowed > 'The Book' from a public library :-) FYI my comments are restricted the PDF floating around of the recommended UNIX and Linux System Admin book. That's definitely not legit. What libraries offer is not only
2018 Dec 30
2
rsync remote raw block device with --inplace
It would be very nice to be able to rsync the raw data content of, e.g., a non-mounted disk partition, particularly in combination with --inplace. Our reality: several dual-boot machines running Windows during the day and Linux at night, during backups. Windows is very tedious and iffy to re-reinstall without a raw disk image to start from. Disks fail, and the ensuing downtime must be
2016 Feb 10
3
Testing Best Practices/Goals (in the context of compiler-rt)
Recently had a bit of a digression in a review thread related to some tests going in to compiler-rt ( http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160208/330759.html ) and there seems to be some disconnect at least between my expectations and reality. So I figured I'd have a bit of a discussion out here on the dev lists where there's a bit more visibility. My basic
2016 Feb 10
3
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
On Wed, Feb 10, 2016 at 2:11 PM, Justin Bogner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > David Blaikie via cfe-dev <cfe-dev at lists.llvm.org> writes: > > Recently had a bit of a digression in a review thread related to some > tests > > going in to compiler-rt ( > > > http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160208/330759.html
2018 Dec 30
3
Aw: Re: rsync remote raw block device with --inplace
> There have been addons to rsync in the past to do that but rsync really > isn't the correct tool for the job. why not correct tool ? if rsync can greatly keep two large files in sync between source and destination (using --inplace), why should it (generally spoken) not also be used to keep two blockdevices in sync ? maybe these links are interesting in that context:
2016 Feb 11
3
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
On Wed, Feb 10, 2016 at 3:55 PM, Alexey Samsonov via cfe-dev < cfe-dev at lists.llvm.org> wrote: > I mostly agree with what Richard and Justin said. Adding a few notes about > the general strategy we use: > > (1) lit tests which look "end-to-end" proved to be way more convenient for > testing runtime libraries than unit tests. > We do have > the latter, and
2016 Feb 13
2
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
On Fri, Feb 12, 2016 at 5:43 PM, Alexey Samsonov via cfe-dev < cfe-dev at lists.llvm.org> wrote: > > > On Thu, Feb 11, 2016 at 1:50 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> On Wed, Feb 10, 2016 at 3:55 PM, Alexey Samsonov via cfe-dev < >> cfe-dev at lists.llvm.org> wrote: >> >>> I mostly agree with what
2016 Feb 17
4
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
On Fri, Feb 12, 2016 at 5:43 PM, Alexey Samsonov <vonosmas at gmail.com> wrote: > > > On Thu, Feb 11, 2016 at 1:50 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> On Wed, Feb 10, 2016 at 3:55 PM, Alexey Samsonov via cfe-dev < >> cfe-dev at lists.llvm.org> wrote: >> >>> I mostly agree with what Richard and Justin
2016 Feb 17
0
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
On Fri, Feb 12, 2016 at 5:48 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Fri, Feb 12, 2016 at 5:43 PM, Alexey Samsonov via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> >> >> On Thu, Feb 11, 2016 at 1:50 PM, David Blaikie <dblaikie at gmail.com> >> wrote: >> >>> >>> >>> On Wed, Feb 10,
2016 Feb 26
3
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
On Fri, Feb 26, 2016 at 1:07 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Wed, Feb 17, 2016 at 8:45 AM, David Blaikie via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> >> >> On Fri, Feb 12, 2016 at 5:43 PM, Alexey Samsonov <vonosmas at gmail.com> >> wrote: >> >>> >>> >>> On Thu, Feb 11,
2016 Feb 26
0
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
On Wed, Feb 17, 2016 at 8:45 AM, David Blaikie via cfe-dev < cfe-dev at lists.llvm.org> wrote: > > > On Fri, Feb 12, 2016 at 5:43 PM, Alexey Samsonov <vonosmas at gmail.com> > wrote: > >> >> >> On Thu, Feb 11, 2016 at 1:50 PM, David Blaikie <dblaikie at gmail.com> >> wrote: >> >>> >>> >>> On Wed, Feb 10,
2016 Feb 26
0
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
Sorry, lost track of this thread. On Wed, Feb 17, 2016 at 8:45 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Fri, Feb 12, 2016 at 5:43 PM, Alexey Samsonov <vonosmas at gmail.com> > wrote: > >> >> >> On Thu, Feb 11, 2016 at 1:50 PM, David Blaikie <dblaikie at gmail.com> >> wrote: >> >>> >>> >>>
2016 Feb 26
0
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
On Fri, Feb 26, 2016 at 1:11 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Fri, Feb 26, 2016 at 1:07 PM, Sean Silva <chisophugis at gmail.com> wrote: > >> >> >> On Wed, Feb 17, 2016 at 8:45 AM, David Blaikie via cfe-dev < >> cfe-dev at lists.llvm.org> wrote: >> >>> >>> >>> On Fri, Feb 12, 2016 at
2016 Feb 26
3
[cfe-dev] Testing Best Practices/Goals (in the context of compiler-rt)
On Fri, Feb 26, 2016 at 1:31 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Fri, Feb 26, 2016 at 1:11 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> On Fri, Feb 26, 2016 at 1:07 PM, Sean Silva <chisophugis at gmail.com> >> wrote: >> >>> >>> >>> On Wed, Feb 17, 2016 at 8:45 AM, David
2017 Aug 10
0
Errors on an SSD drive
On Thu, 10 Aug 2017, mad.scientist.at.large at tutanota.com wrote: > what file system are you using?? ssd drives have different characteristics > that need to be accomadated (including a relatively slow write process which > is obvious as soon as the buffer is full), and never, never put a swap > partition on it, the high activity will wear it out rather quickly. I know this is
2009 Mar 11
1
[PATCH] ocfs2: Fix a bug found by sparse check.
We need to use le32_to_cpu to test rec->e_cpos in ocfs2_dinode_insert_check. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/alloc.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/fs/ocfs2/alloc.c b/fs/ocfs2/alloc.c index 3a9e5de..19e3a96 100644 --- a/fs/ocfs2/alloc.c +++ b/fs/ocfs2/alloc.c @@ -176,7 +176,8 @@ static int
2009 Apr 17
0
The ocfs2.git tree is moving!
ocfs2 fans! The ocfs2.git tree is a little bored with life in the suburbs, and so it is moving to the city! Starting today, I'll be feeding it and watering it at git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2.git. All your usual branchy goodness will be there. Don't worry, Mark still is my co-maintainer. He's done all the heavy tree lifting for over two years, and its
2004 Apr 27
0
[OT] Re: p-values
Greg Tarpinian wrote: > I apologize if this question is not completely appropriate for this > list. > > I have been using SAS for a while and am now in the process of > learning some C and R as a part of my graduate studies. All of the > statistical packages I have used generally yield p-values as a > default output to standard procedures. > > This week I have been