Displaying 9 results from an estimated 9 matches for "impugn".
Did you mean:
imaplgn
2009 Feb 05
3
The Origins of R AND CALCULUS
....
> >>>
> >>> Those of us on this list (with the possible exception of one or two
> >>> nutters)
> >>> would take it that it goes without saying that R was developed on the
> >>> basis
> >>> of S --- we all ***know*** that. To impugn the integrity of Ihaka
> >>> and Gentleman,
> >>> because an article which *they didn't write* failed to mention this
> >>> fact, is
> >>> unconscionable.
> >>>
> >>> cheers,
> >>>
> >>>...
2016 Jul 21
5
[RFC] One or many git repositories?
...it.
And, then, suddenly, in the last day or so, a bunch of support seems to
have shown up for the one-repo solution. Way more than *I'd* ever expected
for sure. Even from people I had thought were super-opposed to it turned
out not to be!
I'm also really sad to hear that people have been impugning your motives,
because you've done a tremendous amount of work to bring this to a
conclusion, and it *really* ought to be clear to everyone that you've been
doing an admirable job of driving towards consensus here, and basically
nothing more.
IMO, the only reason we can even have this co...
2018 Sep 01
2
Certificates
>
> And for other services like IMAP, SMTP, LDAP (maybe not LDAP) constant
> changing certs even with a long lived root may get old for your customers.
Why? I have corporate systems on 2 year commercial CA signed
certificates and personal servers on 90 day LetsEncrypt ones - my users
of IMAP and SMTP have never ever noticed when I changed the
certificates on any device. They
2004 Jan 10
2
Free Software or not -- that's the question /* New subject */
(removed In-Reply-To header)
On Sat, Jan 10, 2004 at 10:01:12AM +0000, WipeOut wrote:
> >>
> >>And make sure to send in a disclaimer otherwise it will not even be
> >>looked at.. :)
> >>
> >How do we know what is disclaimed or not disclaimed?
> >/O
> >
> Digium have all the Disclaimers and will not develop or include any code
> into
2016 Jul 21
3
[RFC] One or many git repositories?
On Wed, Jul 20, 2016 at 5:56 PM, Renato Golin via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On 21 July 2016 at 01:39, Justin Lebar <jlebar at google.com> wrote:
> > This is true if you s/checkout/clone/. With a single repo, you must
> > clone (download) everything (*), but after you've done so you can use
> > sparse checkouts to check out (create a
2010 Dec 01
6
GPL and R Community Policies (Rcpp)
This post asks members of the R community, users and developers,
to comment on issues related to the GNU Public License
and R community policies more generally.
The GPL says very little about protecting the the rights of original
contributors by not disseminating misleading information about them.
Indeed, for pragmatic reasons it effectively assumes that original authors
have no rights regarding
2009 Jun 15
0
books on Time serie
...nt for me to know
> about tcltk if I am to use R, is there an example of the use of tcltk
> that I can see, do I need tcltk to use R, what is the DISPLAY
> variable,
> etc. Further explanation in the WIKI would help, but so would a more
> comprehensive man page. I don't mean to impugn the people who gave
> their
> time to develop the tcltk-package, its man page or the WIKI; their
> work
> is greatly appreciated. I simply took the man page as an example of
> documentation that may not be as well done is the code written to
> perform the functions described b...
2010 Sep 01
2
HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Everyone,
On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their
End of Life and will no longer be supported by the FreeBSD Security Team.
Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD
6.x stable branch, support for the FreeBSD 6.x stable branch will also
cease at the same point. Users of either of
2010 Sep 01
2
HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Everyone,
On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their
End of Life and will no longer be supported by the FreeBSD Security Team.
Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD
6.x stable branch, support for the FreeBSD 6.x stable branch will also
cease at the same point. Users of either of