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

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

2016-03-04 Thread 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 mean doing a >> "pull" on GitHub

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

2016-03-04 Thread Guglielmetti, Robert
On 3/4/16, 2:50 PM, "Georg Mischler" wrote: >> >I'm still figuring this out myself. Here's my current understanding: > >A "pull request" is a request to the maintainer to merge changes from a >branch or a fork into the trunk. Since anyone can easily fork a project, >this

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

2016-03-04 Thread Georg Mischler
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 mean doing a "pull" on GitHub itself? I'm still figuring this out myself. Here's my current understanding: A "pull

[Radiance-dev] GitHub projects on geometry translation

2016-03-03 Thread Georg Mischler
While at it, I created three seperate projects on GitHub: 1. https://github.com/gmischler/Torad Mostly for historical reasons, and to get the hang of the system. 2. https://github.com/gmischler/Dxf2rad-Radout Yes, the two share most of the codebase, and are now available with a MIT license