Re: [Rd] trivial typos in man/switch.Rd

[Kurt Hornik]

> Ben Bolker writes:

Thanks: fixed now in the trunk.

Best
-k

>   My colleague points out that these typos are probably still present
> because almost no-one has the stamina to read that far down in ?switch ...

>   cheers
> Ben Bolker
> x[DELETED ATTACHMENT switch_patch.txt, plain text]
> __
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] R-Forge > GitHub?

[Spencer Graves]

   Thanks so much for your help.


   Now your "git push -u origin master" was "![rejected]", after 
creating a new SSH and after your "git clone" and other "git remote 
rename ..." commands seemed to work:


$ git clone g...@github.com:joshuaulrich/tmp-ecfun.git Ecdat
# Cloning into 'Ecdat'... done.

$ cd Ecdat/
$ git remote rename origin tmp
$ git remote add origin https://github.com/sbgraves237/Ecdat
$ git push -u origin master
#[Username & password OK]
To https://github.com/sbgraves237/Ecdat
  ! [rejected]    master -> master (fetch first)
error: failed to push some refs to 'https://github.com/sbgraves237/Ecdat'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
SpenceravessMBP:Ecdat sbgraves$


   Suggestions?
   Thanks again,
   Spencer Graves


On 2019-07-01 01:05, Ott Toomet wrote:
> Apparently you created id_rsa key pair with a passphrase. Passphrase 
> is like an additional password protection layer on your ssh key.  I 
> don't know how did you create it.  But you can always create a new one 
> (you should delete the old one before you create a new one) using the 
> shell command 'ssh-keygen'.  It asks for a passphrase, just push enter 
> for an empty passphrase (twice).  You also have to update the ssh 
> public key (id_rsa.pub) on github by supplying the new public key 
> (id_rsa.pub).
>
> There are some implications you should be aware of:
> * if you delete id_rsa*, you cannot use any ssh authorization that 
> relies on this key any more (that's why you have to update on GH).  
> From the what you write (... created 2 days ago) I guess you do not 
> use these keys elsewhere but I may be wrong.
> * if you supply empty passphrase, you bypass the optional extra 
> security layer.  I think this is OK for open source software 
> development on your personal computer but your preferences/situation 
> may differ.
> * You cannot use the same keys with passphrase if they are created 
> without one.  This is likely not an issue, but if it turns out to be a 
> problem, you can either add passphrase to the default keys, or create 
> another set of keys, passphrase protected.
>
> Cheers,
> Ott
>
>
> On Sun, Jun 30, 2019 at 9:51 PM Spencer Graves 
> mailto:spencer.gra...@prodsyse.com>> wrote:
>
>
>
> On 2019-06-30 06:58, Joshua Ulrich wrote:
> 
>
> > I imported both packages into separate repositories:
> > https://github.com/joshuaulrich/tmp-ecdat
> > https://github.com/joshuaulrich/tmp-ecfun
> >
> > I changed your email address on your R-Forge commits to match your
> > GitHub email address, so R-Forge commits would be associated
> with your
> > GitHub account.  I also omitted the "move" commit from Ecdat,
> and the
> > "obsolete > GitHub" commits from both packages.  I've attached a
> file
> > with the commands I used, if anyone is interested.
> >
> > You can use my repos by cloning them to your local machine, adding
> > your repos as new remotes, and pushing to them.  You would need
> to run
> > these commands (untested):
> >
> > ### clone my GitHub repo to your machine
> > git clone g...@github.com:joshuaulrich/tmp-ecfun.git Ecdat
>
>
> Thanks so much.  Sadly, I'm still having troubles.  This "git
> clone ..."
> generates:
>
>
> Enter passphrase for key '/Users/sbgraves/.ssh/id_rsa':
>
>
>    Sadly, I don't know the passphrase it's looking for here,
> and I
> don't know how to find what it's looking for.  Under GitHub >
> Settings >
> "SSH and GPG keys", I see an SSH key dated two days ago, when I
> cloned
> Ecdat from within RStudio.  And in "~.ssh" I see files id_rsa and
> id_rsa.pub, both created two days ago.
>
>
>    What do you suggest I try to get past this?
>
>
>    Thanks again for all your help.
>
>
>    Spencer Graves
>
> > cd Ecdat
> > ### rename my GitHub repo remote from 'origin' to 'tmp'
> > git remote rename origin tmp
> > ### add your GitHub repo remote as 'origin'
> > ### NOTE: this should be a new, clean repo.
> > ###    Rename your existing 'Ecdat' so you don't overwrite it
> > git remote add origin https://github.com/sbgraves237/Ecdat
> > ### push to your GitHub repo
> > git push -u origin master
> >
> > Then you need to run similar commands for Ecfun.
> >
> > Best,
> > Josh
> >
> >>>         Thanks,
> >>>         Spencer
> >>>
> >>>
> >>> On 2019-06-29 14:09, Henrik Bengtsson wrote:
>  On Sat, Jun 29, 2019 at 9:43 AM Spencer Graves
>   > wrote:
> > Hi, Ott et al.: