Track your changes to an open-source project with git: Difference between revisions
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
I have used two approaches: | I have used two approaches: | ||
#[[Setting up your own public repo on top of an open-source project]] | #[[Setting up your own public repo on top of an open-source project]] - this is thorough but probably overly complex. | ||
#[[Work on an open-source project from anywhere]] | #[[Work on an open-source project from anywhere]] - this is my current standard approach. |
Revision as of 17:31, 3 September 2010
Here are some of the projects on which I have overlaid my code, with the help of git:
- mythtv
- ampache
- wordpressmu
- recess
- a proprietary project hosted privately behind an openvpn connection
All of these currently use subversion, which git can read from and write to. Some of them (read: "mythtv") are insanely active. Git can help you remain sane while you try to overlay your changes on top of a moving target.
I have used two approaches:
- Setting up your own public repo on top of an open-source project - this is thorough but probably overly complex.
- Work on an open-source project from anywhere - this is my current standard approach.