search for: carpentri

I am currently working on a small database project to track company assets. Right now my Database consists of 3 tables. 1 for the equipment, 1 for the users info, and 1 for the type of equipment. I have all 3 databases working on a model test site using RoR. Where i am having trouble is getting the databases to talk together. I can''t find this answer anywhere else. My main table

Hello, I would like to report 2 very minor typos: 1. help file for package:base function:function The last sentence of the "Technical details" section reads: "This is not normally user-visible, but it indicated when functions are printed." Either "is" is missing ("but it is indicated") or "it" should be replaced by "is" ("but

Have you read the books by Cleveland? His experiments show that most people do better estimating things and comparing things on a linear scale rather than looking at angles and areas (also see http://biostat.mc.vanderbilt.edu/twiki/pub/Main/StatGraphCourse/graphsco urse.pdf) With a dot chart you can set the axis to go from 0 to the total of all groups (see the example I sent before, it could

Hi all, I am using rsync to synchronize across two different filesystems (one is an sshfs mount, while the other one is an xfs). I am synchronizing from the xfs to the sshfs one. The xfs filesystem has a sub-second resolution for modification timestamps, while the sshfs one has a 1-second resolution. My synchronization are always rather slow. When investigating why, I realized that rsync is

On 25/01/2018 6:49 AM, Dirk Eddelbuettel wrote: > > On 25 January 2018 at 06:20, Duncan Murdoch wrote: > | On 25/01/2018 2:57 AM, I?aki ?car wrote: > | > For what it's worth, this is my workflow: > | > > | > 1. Get a fork. > | > 2. From the master branch, create a new branch called fix-[something]. > | > 3. Put together the stuff there, commit, push and

On 25 January 2018 at 06:20, Duncan Murdoch wrote: | On 25/01/2018 2:57 AM, I?aki ?car wrote: | > For what it's worth, this is my workflow: | > | > 1. Get a fork. | > 2. From the master branch, create a new branch called fix-[something]. | > 3. Put together the stuff there, commit, push and open a PR. | > 4. Checkout master and repeat from 2 to submit another patch. | >

On 25/01/2018 2:57 AM, I?aki ?car wrote: > For what it's worth, this is my workflow: > > 1. Get a fork. > 2. From the master branch, create a new branch called fix-[something]. > 3. Put together the stuff there, commit, push and open a PR. > 4. Checkout master and repeat from 2 to submit another patch. > > Sometimes, I forget the step of creating the new branch and I

Hi Duncan! I think there are many users whose first experiences with git where frustrating, and trust me, many people here can relate to your pain. I can certainly say that I can. At first, git makes significant effort to become fluent in seemingly "simple" tasks. I can literally feel your pain right now. But this is the main downside of git: that it can be hard to learn. I overcame

This maybe a silly question and the fact that I need a sanity check might even be weirder, but I''m trying to set realistic expectations for myself. I''ve been reading reading reading AWDWR, Ruby on Rails, some of the PickAxe, and even done a few recipes from Rails Recipes. This is all of two weeks. I feel that I''ve learned a considerable amount but going through the

As a newcomer to Asterisk, you will not be welcomed with open arms. First, you will find almost no documentation on it's features. Second, if you try to ask questions, you will be flamed and pointed to worthless how-tos and 'the wiki'. These worthless documents can only be useful for explaining how things work to those already in-the-know. Lastly, Asterisk is so bug ridden, expect