|
From: Christian B. <bor...@de...> - 2011-03-02 11:45:51
|
Am 26.02.2011 14:46, schrieb Bart Van Assche: > Hello Julian, > > Maybe it would be easier for the people who are porting Valgrind if > both Valgrind and VEX would be available in a public git repository ? > Instead of filing patches in the KDE bugzilla people who are porting > Valgrind could set up a clone of the public Valgrind git repository > and work in that repository. That would not only make reviewing those > patches easier but would also make merging them easier -- all that > would be necessary to merge such work is to issue a "git pull" > request. A brief guide about how to import a Subversion repository > into git can be found here: http://help.github.com/svn-importing/. I second Barts opinion. Git (or mercurial) would allow private branches and Julian doesnt have to do anything to make that work (e.g. setting up the svn users). This would help in several cases: 1. For example after we merge the s390 port (hint hint :-) ) I certainly have additional patches later on (new cpus etc.) but some aspects are to big to communicate efficiently via patches. One example is decimal floating point. Its available on power and s390 (with some plans for x86 as well AFAIK) so it would certainly make sense that Maynard and myself would work out the necessary common code changes to work for both system before we bother you. So we could have a decimal floating point tree where Power and s390x can work together until we are satisfied with the result. 2. Another potential benefit would be that Julian could spread the maintenance work among other people. e.g. we could have a trivial bug fix tree maintained by someone you trust and you would just pull once in a while. Christian |