Hello. On Sat, 2014-05-03 at 23:57, Cedric BAIL wrote: > Hello, > > On Sat, May 3, 2014 at 9:53 PM, Daniel Juyung Seo <[email protected]> > wrote: > > Well, I don't think this can go in at this stage as we're in a feature > > freeze. > > Yes and no :-) It has been discussed on IRC (we should have pointed > that on the ML to), but as it is not a public API, is not used by > anything inside our build, and we want people to look at the result > early, it was decided that this could still get in during this week > (The patch has been in discussion for some time on phab already).
Indeed I agreed to put it in at this late phase in the process. I asked for it to be done before beta1 and that it should not interfere with other parts. I have to say I regret giving the ok now that it causes so much trouble. > > This also broke the build. > > Can you check this again? > > This is something I tried to understand but the build break in the > middle of nowhere and I couldn't make sense of it. So I was thinking > it was a temporary failure, if anyone has a better explanation :-) Well, it turned out you had to do 6 or more commits to get this build somehow back again. I still need to understand what I need to change in the mingw build to have it back again. Really not what I was looking for when I agreed on getting it merged. regards Stefan Schmidt ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
