On Thu, 16 Feb 2012 21:34:42 -0800 (PST) Darrell Anderson humanreadable@yahoo.com wrote:
It is an occasion of taking advantage of using git :) You can now clone the Trinity git repository in a public location (for example: gitorious, github, a server you have access on, etc.) and git won't discriminate your repo against Tim's one. So you can have your own git repo you update regularly from Tim's one, apply you own patches to it, and once the patches are applied, you can ask Tim to import your patches from your repo to his.
I don't know whether I did not explain myself well or whether your response is intended to be tongue-in-cheek. :)
I'm already patching from my own local GIT repository. I also have submitted many patches upstream. I could do so for a long time, but that does not do anything to the main project GIT repository because I do not have commit access.
Let me rephrase: if Tim became unavailable for a long period or forever, do we have a plan in place to continue the project or does Trinity fizzle away without Tim?
When you clone a SVN repo, you have a local copy that is subordinated to the remote master. But when you clone a git repo, your clone is technically the same as a git repo, and you can host a public clone of the repo, which could has a purpose such as having a repo that always builds on Slackware ;) (for example https://github.com/torvalds/linux is a public clone of the kernel.org git repository, managed by Linus Torvalds himself) And if the Slackware-related repository is the only active one, it will be the new up-to-date Trinity repository :)
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting