search for: foonly

Displaying 20 results from an estimated 26 matches for "foonly".

Did you mean: soonly
2004 Apr 20
2
Creating variable names
My apologies for asking what is doubtless a dumb question, but I have scant experience in R. It would be very convenient in doing lots of plots to be able to do them in a loop that stepped through a vector of variable names. For example one could say x<-("mydates") y<-c("foo1","foo2","foo3") #where "foon" were vectors
2004 Jun 03
3
Sloppy argument checking for named arguments
Christian -- This is not a bug, but a feature, and the dot is not the issue here. R uses partial argument matching on function arguments. So: > f <- function(foobar = 0){print(foobar)} > f function(foobar = 0){print(foobar)} > > f(fo=1) [1] 1 > f(foo=1) [1] 1 > f(foob=1) [1] 1 > f(fooba=1) [1] 1 > f(foon=1) Error in f(foon = 1) : unused argument(s) (foon ...)
2002 Dec 20
1
"force group" not working with shared directories
...eal with both file-locking and group ownership. I have read that I need essentially the following in my smb.conf file: [lab] path = /usr2/lab available = yes public = yes guest only = no writeable = yes browseable = yes valid users = foonly, hart only user = no oplocks = No level2oplocks = No create mask = 770 directory mask = 770 force group = lab with the important lines being "create mask", "directory mask" and "force group". The problem is that while...
2016 Jun 08
2
Intended behavior of CGSCC pass manager.
On Wed, Jun 8, 2016 at 9:39 AM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > On Wed, Jun 8, 2016 at 4:19 AM, Sean Silva <chisophugis at gmail.com> wrote: > >> Hi Chandler, Philip, Mehdi, (and llvm-dev,) >> >> (this is partially a summary of some discussions that happened at the >> last LLVM bay area social, and partially a discussion about
2012 Nov 15
1
referring to earlier SVN commits
...ollowed by a committer email address, followed by ':' and a 1-origin sequence number if the date/time pair is not unique in the repository; it refers to a commit without being VCS-specific. Thus, instead of "commit 304a53c2" or "r2355", "2011-10-25T15:11:09Z!fred at foonly.com". - http://www.catb.org/~esr/reposurgeon/reposurgeon.html Also, once we transition to native Git repositories, you will be able to amend the most recent commit before you push. This should reduce the number of "typo in previous commit" messages. -- Charles Lepple clepple at g...
2016 Jun 08
2
Intended behavior of CGSCC pass manager.
On Wed, Jun 8, 2016 at 3:10 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Jun 8, 2016, at 2:54 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > > On Wed, Jun 8, 2016 at 9:39 AM, Daniel Berlin <dberlin at dberlin.org> wrote: > >> >> >> On Wed, Jun 8, 2016 at 4:19 AM, Sean Silva <chisophugis at gmail.com> wrote:
2016 Jun 08
12
Intended behavior of CGSCC pass manager.
Hi Chandler, Philip, Mehdi, (and llvm-dev,) (this is partially a summary of some discussions that happened at the last LLVM bay area social, and partially a discussion about the direction of the CGSCC pass manager) A the last LLVM social we discussed the progress on the CGSCC pass manager. It seems like Chandler has a CGSCC pass manager working, but it is still unresolved exactly which
2016 Jun 08
0
Intended behavior of CGSCC pass manager.
----- Original Message ----- > From: "Sean Silva via llvm-dev" <llvm-dev at lists.llvm.org> > To: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Wednesday, June 8, 2016 6:19:03 AM > Subject: [llvm-dev] Intended behavior of CGSCC pass manager. > Hi Chandler, Philip, Mehdi, (and llvm-dev,) > (this is partially a summary of some discussions that
2016 Jun 08
3
Intended behavior of CGSCC pass manager.
Sent from my Verizon Wireless 4G LTE DROID On Jun 8, 2016 1:58 PM, Mehdi Amini <mehdi.amini at apple.com<mailto:mehdi.amini at apple.com>> wrote: > > >> On Jun 8, 2016, at 9:32 AM, Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: >> >> >> ________________________________ >>> >>>
2016 Jun 08
2
Intended behavior of CGSCC pass manager.
> On Jun 8, 2016, at 9:32 AM, Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > From: "Sean Silva via llvm-dev" <llvm-dev at lists.llvm.org> > To: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Wednesday, June 8, 2016 6:19:03 AM > Subject: [llvm-dev] Intended behavior of CGSCC pass manager. > > Hi Chandler,
2016 Jun 08
2
Intended behavior of CGSCC pass manager.
On Wed, Jun 8, 2016 at 12:31 PM, Xinliang David Li <davidxl at google.com> wrote: > > > On Wed, Jun 8, 2016 at 4:19 AM, Sean Silva <chisophugis at gmail.com> wrote: > >> Hi Chandler, Philip, Mehdi, (and llvm-dev,) >> >> (this is partially a summary of some discussions that happened at the >> last LLVM bay area social, and partially a discussion
2016 Jun 09
2
Intended behavior of CGSCC pass manager.
On Wed, Jun 8, 2016 at 8:14 PM, Xinliang David Li <davidxl at google.com> wrote: > > > On Wed, Jun 8, 2016 at 4:38 PM, Sean Silva <chisophugis at gmail.com> wrote: > >> >> >> On Wed, Jun 8, 2016 at 12:31 PM, Xinliang David Li <davidxl at google.com> >> wrote: >> >>> >>> >>> On Wed, Jun 8, 2016 at 4:19 AM, Sean
2012 Jul 26
4
Time rsYnc Machine (tym)
http://dragoman.org/tym Regards Tomas
2003 Dec 04
8
[Bug 769] dh-group-exchange should be configurable off in client and server
http://bugzilla.mindrot.org/show_bug.cgi?id=769 Summary: dh-group-exchange should be configurable off in client and server Product: Portable OpenSSH Version: 3.7p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo:
2016 Jun 08
2
Intended behavior of CGSCC pass manager.
On Wed, Jun 8, 2016 at 12:36 PM, Sanjoy Das via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > Does it make sense to change RefSCCs to hold a list of > RefSCC-DAG-Roots that were split out of it because of edge deletion? > Then one way to phrase the inliner/function pass iteration would be > (assuming I understand the issues): > >
2016 Jun 16
5
Intended behavior of CGSCC pass manager.
On Tue, Jun 14, 2016 at 11:29 PM, Xinliang David Li <davidxl at google.com> wrote: > > > On Thu, Jun 9, 2016 at 3:26 AM, Sean Silva <chisophugis at gmail.com> wrote: > >> >> >> On Wed, Jun 8, 2016 at 8:14 PM, Xinliang David Li <davidxl at google.com> >> wrote: >> >>> >>> >>> On Wed, Jun 8, 2016 at 4:38 PM, Sean
2002 Dec 21
0
Re: samba digest, Vol 1 #2006 - 24 msgs (Out of the office - Returning Monday, Jan. 6th)
...ership. > > I have read that I need essentially the following in my smb.conf file: > [lab] > path = /usr2/lab > available = yes > public = yes > guest only = no > writeable = yes > browseable = yes > valid users = foonly, hart > only user = no > oplocks = No > level2oplocks = No > create mask = 770 > directory mask = 770 > force group = lab > > with the important lines being "create mask", "directory mask" and "force &g...
2013 Mar 18
0
[linux-linus test] 17325: regressions - trouble: broken/fail/pass
flight 17325 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17325/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 guest-start fail REGR. vs. 12557 test-amd64-i386-xl-credit2 15 guest-stop fail REGR. vs. 12557 test-amd64-i386-xl 15 guest-stop
2013 Mar 29
0
[linux-linus test] 17454: regressions - FAIL
flight 17454 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17454/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail
2013 Apr 10
0
[linux-linus test] 17612: regressions - FAIL
flight 17612 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17612/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail