Re: [R-SIG-Mac] Contributing to documentation [Was: Installing gfortran]

2022-04-30 Thread Duncan Murdoch
On 30/04/2022 1:10 p.m., Jeff Newmiller wrote: Re revision numbers... yes, you might have to take care to handle aligning the baseline code against which the patch was generated manually. Given that outside contributions would tend to start from specific releases though this shouldn't be too

Re: [R-SIG-Mac] Contributing to documentation [Was: Installing gfortran]

2022-04-30 Thread Jeff Newmiller
Generating patch files is one of the most fundamental capabilities of git. Changes to the Linux kernel are (almost?) universally submitted via patch files generated from git. Re git and empty directories... git is structurally incapable of recording them in the repo. A common workaround is to

Re: [R-SIG-Mac] Contributing to documentation [Was: Installing gfortran]

2022-04-30 Thread Duncan Murdoch
On 30/04/2022 9:53 a.m., Patrick Schratz wrote: If that is the case, why not contribute to the documentation? That is the whole point of an open source project after all. Because often it is not easily accessible, e.g. living in an ancient SVN repo or lacking (an easy) and clear