Porting Torchat on GIT - Githubissues

I don't think so. It would only make things more complicated for me. It's not 
like there are currently hundreds of people simultanuosly working on hundreds 
of fundamentally different branches, its more like a one-man show at the moment 
and for a typical one-man show there exists nothing more simple than a simple 
svn commit. 

To send me a patch (equivalent of sending me a pull request) you can just make 
your changes in your local working copy of trunk, if you see me updating the 
trunk while you are still working then simply do an "svn up" to merge my 
changes into your's (somewhat similar to rebasing your branch to my master) and 
when finished simply do an "svn diff" and attach it to a bug report.

svn up and svn diff is essentially all one needs to know about svn to 
participate. With git the same task is at least twice as complicated (and more 
confusing for the occasional user).

You can still use git locally to better manage different versions of your own 
copy locally if this better suits your workflow but in the end you still need 
to eventually make it merge with my trunk, you would need to solve potential 
conflicts anyways, with or without git. 

Imho at the moment Torchat code in trunk changes so slowly that it is easily 
possible to do almost anything in trunk, conflicts during svn up will be few, 
if any.
Original comment by prof7...@gmail.com on 28 Dec 2011 at 7:05
SK-Yang / torchat

Porting Torchat on GIT #115
