Am 2016-03-05 02:42, schrieb Randolph Fritz:
On Mar 4, 2016, at 1:50 PM, Georg Mischler <schor...@schorsch.com>
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 itself?
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 seems the easiest way to contribute smaller or occasional fixes.
So what’s the sequence? First I clone the repo, so I have my own copy,
make some changes on my own copy, test them, commit them locally,
decide to submit them, and then what do I do to upload them to you for
consideration?
Git terminology may be confusing at times. This helped me quite a bit:
https://help.github.com/articles/github-glossary/
The typical situation is to create a "fork" first, which will give you
a copy of the project on GitHub. The fork will maintain its connection
to the original, so it can be merged back later.
In contrast, "cloning" means to pull something to your local system
for editing.
Once you have commited and pushed your changes to the fork, you can
then send a pull request to the original project.
Pull requests should really be called "merge requests".
Technically, the same effect could be had by creating a branch within
the original project. A fork has the advantage that the original author
doesn't get involved until changes have been made, hopefully tested,
and a pull request comes in about them. You can probably best think
of a fork as an "external branch".
Anything else we'll just have to experiment with, as soon as the
opportunity arrives.
-schorsch
--
Georg Mischler -- simulations developer -- schorsch at schorsch com
+schorsch.com+ -- lighting design tools -- http://www.schorsch.com/
_______________________________________________
Radiance-dev mailing list
Radiance-dev@radiance-online.org
http://www.radiance-online.org/mailman/listinfo/radiance-dev
