On Tue, Feb 15, 2011 at 10:07 AM, Tom Hacohen <tom.haco...@partner.samsung.com> wrote: > On Tue, 2011-02-15 at 20:00 +0900, Carsten Haitzler wrote: >> +1 ... as long as we understand that these are guidelines and we SHOULD stick >> to them as much as possible - but people will make mistakes and stuff will >> slip >> through - but a lot LESS will slip through that if we didn't. :) > > The same way we handle compilation errors ;P > > Since everyone (who replied) approved I think it's time for me to > summarize the changes into wiki/another email and send everyone a > notification of start-of-enforcement. > > OK? > Warning: if no one will response by Thursday I'll just go ahead :P
+1 as well, I already said on IRC... but here goes the official one. Also, as talked at IRC: - GIT->SVN tool, it will work with patches created with git format-patch, including binary patches (yes, NOW it does, I fixed all bugs). It will handle correct 'svn mv', 'svn add' or 'svn rm' for you. http://barbieri-playground.googlecode.com/svn/python/svn-git-am.py - My previous attempt to fix the same issue months ago: http://www.mail-archive.com/enlightenment-devel@lists.sourceforge.net/msg27084.html Unfortunately people turned it into a SVN x GIT and it never worked out. Let's hope it will work now. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
