On 10 June 2010 02:57, Chow Loong Jin hyperair@gmail.com wrote:
On Wed, 09 Jun 2010 18:15:02 +0200 Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 09.06.2010 18:09, schrieb Nick Treleaven:
On Wed, 09 Jun 2010 15:11:48 +0200 Thomas Martitzthomas.martitz@student.htw-berlin.de wrote:
>> Am 09.06.2010 03:40, schrieb Lex Trotman:
>>> Sure its easier if everyone is using git, but ATM this is an SVN >>> project.
>> Although most, if not all, geany developers use git, don't they?
> Do you mean git-svn? The Git repo is not writable.
Yes, to me it looks like the vast majority of contributors use git (and git svn to commit to the geany/geany-plugins svn). My perception may not be very accurate though.
I don't use Git for Geany, but wouldn't mind if everyone else wants to switch to it.
Maybe it would be a good time to consider it in a serious manner. I would very much appreciate a switch to git :) OTOH my opinion doesn't matter very much, I guess.
If Geany switches, I'd love for geany-plugins to switch as well.
The switch to a dvcs would be useful since local version control would then be integrated with the main vcs (if you wanted it to be).
If Geany switches then the process needs to be decided and promulgated first.
Can personal branches be hosted on your host or only branches created by you, allows sm, the new unstable and bs to operate mostly like now, separate but globally visible. Who is your host?
Who has permissions to do what, Git can have very fine control over who can do what.
What workflow are you going to follow? eg stable branch only releases are committed to, unstable that reviewed changes and patches are committed to? or what?
Having both SVN and Git committable is difficult so everyone would have to switch.
As usual the problems are non-technical ones :)
Cheers Lex
-- Kind regards, Chow Loong Jin
Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel