Re: s/.*_moc.cpp/moc_\1.cpp

2008-11-14 Thread Andre Poenitz
On Fri, Nov 14, 2008 at 02:55:26PM +0100, Jürgen Spitzmüller wrote: > Andre Poenitz wrote: > > Jean-Marc had the same idea. > > Excellent. Now the fun can begin, I guess :-) > > BTW feel free to backport fixes to the new branch while you are sober. > Just put them in if you are confident enough (

Re: s/.*_moc.cpp/moc_\1.cpp

2008-11-14 Thread Jürgen Spitzmüller
Andre Poenitz wrote: > Jean-Marc had the same idea. Excellent. Now the fun can begin, I guess :-) BTW feel free to backport fixes to the new branch while you are sober. Just put them in if you are confident enough (this only applies for the meeting, of course). Jürgen

Re: s/.*_moc.cpp/moc_\1.cpp

2008-11-14 Thread Andre Poenitz
On Fri, Nov 14, 2008 at 02:40:06PM +0100, Jürgen Spitzmüller wrote: > Andre Poenitz wrote: > > Unless someone complains very loudly soon I'll change the naming of > > our generated moc files to the "more standard" moc_*.cpp scheme. > > Makes interaction with one of the tools I'd like to use simpler

Re: s/.*_moc.cpp/moc_\1.cpp

2008-11-14 Thread Jürgen Spitzmüller
Andre Poenitz wrote: > Unless someone complains very loudly soon I'll change the naming of > our generated moc files to the "more standard" moc_*.cpp scheme. > Makes interaction with one of the tools I'd like to use simpler. But please remember to create an 1_6_X branch before breaking trunk into

s/.*_moc.cpp/moc_\1.cpp

2008-11-14 Thread Andre Poenitz
Unless someone complains very loudly soon I'll change the naming of our generated moc files to the "more standard" moc_*.cpp scheme. Makes interaction with one of the tools I'd like to use simpler. Andre'