Re: [Radiance-dev] GitHub projects on geometry translation

2016-03-05 Thread Randolph Fritz
> Actually, I'm not absolutely certain on which project you'll have to press > "New Pull Request", but that will be easy to find out. I’m pretty sure it’s on yours, since you’re the one who receives the pull request. > I've probably been guilty of your #6 myself… :-) Randolph

Re: [Radiance-dev] GitHub projects on geometry translation

2016-03-05 Thread Georg Mischler
Am 2016-03-05 20:26, schrieb Randolph M. Fritz: Pronoun troubles: who is doing what to which where? So is this correct: * I first use the "fork" button to create my own copy of the repository on GitHub * Then I use "git clone" on my own system, referencing my fork. This

Re: [Radiance-dev] GitHub projects on geometry translation

2016-03-05 Thread Randolph M. Fritz
Pronoun troubles: who is doing what to which where? So is this correct: 1. I first use the "fork" button to create my own copy of the repository on GitHub 2. Then I use "git clone" on my own system, referencing my fork. This downloads the repository to my system 3. Commit my

Re: [Radiance-dev] GitHub projects on geometry translation

2016-03-05 Thread Georg Mischler
Am 2016-03-05 02:42, schrieb Randolph Fritz: On Mar 4, 2016, at 1:50 PM, Georg Mischler wrote: Am 2016-03-04 22:09, schrieb Randolph M. Fritz: "For code fixes, the standard Git method seems to be pull requests." Well, but eventually you have to push them. Or do you