Comment #7 on issue 2217 by [email protected]: Patches tutorial
http://code.google.com/p/sympy/issues/detail?id=2217
I don't understand something.
You have written that 'The user should always clone from
git://github.com/sympy/sympy.git. Otherwise, he will not be able to pull in
new changes with git pull'
But [1] offer this way for solving it:
# Assigns the original repo to a remote called "upstream":
git remote add upstream git://github.com/sympy/sympy.git
git fetch upstream
I also have added in [2] section `Synchronization with master sympy/sympy`
about it.
On the one hand I also tend to use `origin` remote name only for read-only
`sympy/sympy` repository. In this case the difference between "Quick patch"
way and "GitHub variant" way will be minimal, and the document [2] will be
less tangled.
On the other hand, if `origin` will be assigned to `sympy/sympy`, then
deviation from [1] will be. If someone will be checked for more information
with [1] then he might to be tangled too. And I am not sure, that now all
learn how to send a path by our document.
[1] http://help.github.com/fork-a-repo/
[2] https://github.com/sympy/sympy/wiki/Development-workflow
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy-issues?hl=en.
