features."
>
> I do not think relying on a beta build system that may change incompatibly
> at any time is a good idea.
To be fair, it has time to leave that state and provide compatibility.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect
ave an IDE of ours means this one should be reasonably easy
to address, as we can make that IDE work with the tool. So long as the tool is
actually toolable, of course.
"More than one" would be quite a challenge.
> B) Should be easy to hook in static and dynamic code analyzer tools
relating our experience.
You brought Kata Containers up. If you use containers on Linux and you care
about security, you should take a look at it. It's about using the processor's
virtual machine hypervisor functionality to make sure the code in the
container can't break out of the co
urn to for help. I want to say the same for the tool
we choose.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
enSUSE:Factory/standard/x86_64/
libqt5-qtbase/_log
On lines 1056-1059, you see CFLAGS and CXXFLAGS being set. But then if you
scan forward in the actual build, you don't see any of them applied.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technol
ualifies Samuel for the approver status.
Another "what? he's not an approver?" case.
+1 from me.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing lis
On Monday, 16 July 2018 08:50:05 PDT Thiago Macieira wrote:
> On Monday, 16 July 2018 00:08:44 PDT Bogdan Vatra via Development wrote:
> > The clang support was added and works fine from 5.9. But I think is too
> > late to switch NDK for 5.11.
>
> I'm not asking to cha
On Sunday, 29 July 2018 11:15:38 PDT BogDan Vatra via Development wrote:
> AFIK qt 5.12 will use ndk r16 or better.
The question was for Qt 5.11 using fixed headers.
The fix in Bionic happened in January 2015.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - In
e a file Android doesn't have
# undef _PATH_MOUNTED
# define _PATH_MOUNTED "/proc/mounts"
#endif
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing
braries: we work with the latest, unless that
release happened too late in our own release cycle.
But where do we get LLVM from on a Mac? Is it from Apple? If so, we may need
to keep things working with an old, patched version, in addition to the
latest. Or we require an upgrade with Homebrew.
are qbs and CMake.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
> This would probably require some major hackery in the build system. No idea
> whether this is supported also on other platforms, and how hard it would be
> to pull it off. I'm not volunteering
We don't need it in all platforms, but this post-processing step isn't a
a files?
> It however does not protect us from the issue on Windows and macOS, but it
> covers the cross-platform code.
nm exists on both too. We won't get it on MSVC, though.
--
Thiago Macieira - thiago.macieira (AT) intel.com
should erase your
MinGW installation and install another.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-projec
27;re not
switching Qt just yet, so if you're saying the tool is ready, get others to
use it now.
[*] I was there in Akademy 2005 when we decided to use Scons because CMake's
language was too ugly.
--
Thiago Macieira - thiago.macieira (AT) i
And it creates
a fairly comprehensive log file, similar to qmake's -d output. Debugging
automake is a different story, but it's a very limited tool. And don't try to
debug libtool (you can live an entire lifetime using it and never debug it).
--
Thiago Macieira - thi
dn't know about those.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
s builds both frameworks and no-frameworks,
though I think I haven't built the latter in several years (unlike the Mac and
Windows laptops, the Mac machine is from 2012, so it has old stuff).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
27;d like to start using 'qlc' as prefix. See also
> > change https://codereview.qt-project.org/#/c/235631/ for qtbase.
>
> Namespaces doesn’t work for that?
Namespaces do. Unnamed namespaces don't (used across multiple files).
--
Thiago Macieira - thiago.macieira
On Tuesday, 31 July 2018 07:52:37 PDT Thiago Macieira wrote:
> Well, it could be much worse. There are a couple of low-hanging fruits
> there that we can easily fix. I'll take a look later today on those
> applying to QtCore.
Done almost all for qtbase, from Kai's listing:
ht
; Android where we can bundle multiple platforms in the same package.
Agreed.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http:/
On Wednesday, 1 August 2018 13:14:32 PDT Sérgio Martins wrote:
> On Sat, Jul 21, 2018 at 3:35 AM, Thiago Macieira
>
> wrote:
> > Hello
> >
> > Having spent far too much time trying to figure out why crappy
> > buildsystems
> > cause failures in distros (li
cool feature.
Now that is nice, as we know that the moc, uic, rcc outputs are platform-
independent. That should help reduce the build times on Windows for debug-and-
release builds, as running moc is a significant portion of the build time.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Qt SDKs, this way we'll save a lot of space.
Sorry, I didn't get it. Can you clarify?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
ld change, as QT_NO_DEBUG changes.
Someone could #ifdef on it and add properties, signals or slots based on it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mai
one that in my mind is "significant portion of the build" and
Simon is right that we can't share its output.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development ma
ot easy to achieve.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Thursday, 2 August 2018 10:36:11 PDT Konstantin Tokarev wrote:
> Do you have any prominent examples?
No, sorry. We don't need to cross-compile at the company I work for :-)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technolog
ch-dependent dir. That would mean splitting the "qml" dir in two:
/lib/qml
/share/qml
I don't see us spending the effort...
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
y on the critical build path, due to its size.
Doubling the build time by inserting a dependency of equal size is not going
to make you friends.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
__
version from Microsoft for 5.12 if we can agree on this change.
Agreed, please switch to the Microsoft one and let's try and reduce our patch
list (technical debt). Having instructions on how to build with an external
ANGLE, possibly installed via vcpkg, would be very welcome.
--
Thiago Macieira
On Thursday, 2 August 2018 23:03:06 PDT Martin Koller wrote:
> QT_FORWARD_DECLARE_CLASS(QTimer)
Easier to just put QT_BEGIN_NAMESPACE before and QT_END_NAMESPACE after. It's
more verbose, but it's actually easier to read.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Softw
e the bug when the first branch gets the fix. When the other
branches get it, I just update the bug report with an extra Fix For and SHA-1.
This is a nice way for the script to do the same.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Tec
On Tuesday, 7 August 2018 02:46:12 PDT Frederik Gladhorn wrote:
> The plan is to update the fix versions and close the task as done when a
> line in the commit message starts with "Fixes:".
Thanks, Frederik!
Please update the changelog-creation script to detect this keyword
ers. If you want it, you have to obtain a commercial license.
But if you upgrade to 5.9, you get qmlcachegen. Note that the cachegen tool is
not a replacement for the compiler: it's a cache. The source of the QML still
needs to be present somewhere.
--
Thiago Macieira - thiago.macieir
On Wednesday, 8 August 2018 02:58:08 PDT Frederik Gladhorn wrote:
> branch is x.y -> find the next valid patch version
Suggestion: use the x.y release and when we make that release, we rename it in
JIRA.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Inte
compile qml application with qmake?
Yes, you can compile with qmake as well as cmake or other solutions.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Develop
uld then
> automatically mark fixes targeting the x.y branch as x.y.(z+1)
Why can't the renaming in JIRA be done at that exact time? That way, we
wouldn't get a mass update of tasks with the version changed.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect
their own, erase them all
too.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
lease give us a bit more than 24 hours since
the compiler release to know more.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
On Wednesday, 15 August 2018 08:58:22 PDT Thiago Macieira wrote:
> If you upgraded MSVC 2017 to 15.8 yesterday and you try to build qtbase,
> you'll get a build error. This is fixed, but you need to make sure you erase
> .qmake.stash files everywhere, since they contain the cached
d work:
value[1]["hello"][32] = false;
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-pro
Converting from JSON is lossless and converting that content back to JSON is
lossless too. It's just not particularly efficient today.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
__
ternals with
QCborContainerPrivate. That way, the conversion from JSON to CBOR is O(1) and
the conversion backwards is just a validation.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
__
On Sunday, 8 July 2018 17:15:36 PDT Thiago Macieira wrote:
> This is the second time I've run into a compiler bug with that XCode's
> ancient Clang.
Third strike.
Can we PLEASE REMOVE ancient Clang that is running on macOS 10.11 in the CI
for 5.12? Yes, I've read the emai
year before the fact. So if we'd like to drop in
5.14, we should include the announcement in the 5.12 changelog.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing
On Thursday, 23 August 2018 23:03:43 PDT Thiago Macieira wrote:
> Since we're talking about macOS 10.11 and I came across the Windows support
> lifetime pages, I'm posting this for future reference.
>
> https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fac
we had THREE minor releases of Qt in 2017? 5.8
(Jan 20), 5.9 (May 29) and 5.10 (Dec 5).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-proje
e using Qt for applications that run on those offline
computers, I don't mind keeping support.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@q
On Monday, 27 August 2018 01:50:46 PDT André Pönitz wrote:
> On Mon, Aug 27, 2018 at 12:00:17AM -0700, Thiago Macieira wrote:
> > I don't have a problem with that, so long as they never connect those
> > computers to the Internet after January 2020. That would be irresponsi
nly if
it isn't too difficult to do so.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
ading?
Rewrite using techniques and classes that are accelerated using OpenGL. Like
QtQuick.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Developmen
pted to say that it
> would even be possible to implement the Qt/Widgets API on top of Qt/Quick
> core.
So long as you ditch the paint event for most of the classes, leaving the
QQuickPaintedItem (or whatever it's called) only for the cases where it's
truly needed.
--
Thiago Maciei
On Thursday, 30 August 2018 08:46:32 PDT Uwe Rathmann wrote:
> On Thu, 30 Aug 2018 07:50:41 -0700, Thiago Macieira wrote:
> > The result of (b) is a retained-mode scene graph. It's in the QtQuick
> > library.
>
> I know, but now we have Qt 5.11 and it is fair to review
ou need the performance of graphics, you need to use the
GPU the way the GPU is designed. Reduce your CPU work and use more retained
settings across frames.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Ope
s (Gunnar and Kim) working on
figuring out how to write proper code to use the GPU the way the GPU is meant
to be used. This event is what I am calling the end of the OpenGL paint engine
experiment and the birth of the scene graph.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Softwa
aintainers'. You're
not including the pathological cases where the X11 graphics system didn't
perform as well and required the raster engine to kick in. And you're not
including the need to produce the exact same result in all platforms.
--
Thiago Macieira - thiago.macie
system to "native" - the default since 4.8 is raster.
Please note Qt 4 is out of support, is not receiving security updates and has
known security problems. It would be irresponsible to use it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Archi
On Tuesday, 4 September 2018 08:16:34 PDT Cristian Adam wrote:
> On Tue, Sep 4, 2018 at 4:46 PM Thiago Macieira
>
> wrote:
> > Please note Qt 4 is out of support, is not receiving security updates and
> > has
> > known security problems. It would be irresponsible to
closed because of not fixing the X11 paint engine
> anymore.
This being the reason why the X11 engine is not good for everyone.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_
I guess I didn't test non-ASCII content.
moc was changed recently to save data in CBOR format instead of our binary
JSON.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Wednesday, 5 September 2018 09:57:30 PDT Thiago Macieira wrote:
> On Wednesday, 5 September 2018 00:20:22 PDT Helio Chissini de Castro wrote:
> > jsonplugin2.moc:153:1: error: narrowing conversion of ‘'\303'’
> > from ‘char’ to ‘unsigned char’ inside { } [-Wnar
r, it's
still got a few rough edges, so it wouldn't make sense to announce yet either.
As soon as it's usable, it should appear in the ChangeLog.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
On Wednesday, 5 September 2018 12:57:39 PDT Uwe Rathmann wrote:
> On Wed, 05 Sep 2018 09:55:41 -0700, Thiago Macieira wrote:
> >> It also raises questions about the status of the X11 paint engine.
> >> Several bugs have been closed because of not fixing the X11 pain
lying around. Make
sure it's a completely clean build and that the older version of Qt is not
anywhere to be found.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Develop
On Thursday, 6 September 2018 05:38:08 PDT Helio Chissini de Castro wrote:
> No, still getting same error.
Updated. I made a signed-char error:
if (c < 0x20)
is true for non-ASCII when chars are signed.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Inte
orValueRef::operator[](...) doesn't exist:
>
> qDebug() << array[1]; // OK
> qDebug() << array[1][2]; // ERROR C2676: 'QCborValueRef' does not
> define this operator or a conversion to a type acceptable to the
> predefined operator
That&#x
The issue with map["hello"] can be an API review issue, though.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
ht
d another application's window
(for example, VirtualBox for the guest window)? And how do they find out the
real pixel size of it, in case scaling is active?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
nfo.html
I could see kwin_x11 needing it, but I really don't see all the other
applications doing so. Do we have a replacement for QX11Info?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source T
rror: undefined reference to 'qt_open64(char const*, int, unsigned int)'
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
ht
nds like the nicer way to
> do it, so that I can make a Qt6 shadow build of dev branch at any time.
A configure option that overrides the MODULE_VERSION variable from .qmake.conf
should be easy.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect -
keeping the old module
working for their applications (or Linux distribution, though I can't find
any). They may also be (ab)using QLibraryInfo::ImportsPath for some other
purpose.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software A
t passes through the copy constructor, not the move
one. We cana add an extra move constructor for const QCborValue && if
necessary.
Eddy: what happens in the new API if you write:
const QCborArray array = { QCborArray{ 1 } };
QCborValue v = array[0];
v[0] = 2;
Does that mod
On Friday, 5 October 2018 08:35:10 PDT Thiago Macieira wrote:
> Cons:
> Suppresses move construction as in
> QCborValue v = array[n];
> this still compiles, but passes through the copy constructor, not the move
> one. We cana add an extra move constructor for const Q
On Saturday, 6 October 2018 05:45:47 PDT NIkolai Marchenko wrote:
> Doesn't that mean that Controls will also get the boot though?
No, QtQuickControls1 is a QtQuick2 framework.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technolog
er. We still have
architectures where they don't.
Another aspect is that the macro assembler headers don't get installed and
aren't subject to syncqt.pl, so their hierarchy is a lot simpler than for Qt's
own headers.
I recommend against changing Qt.
--
Thiago Macieira -
mount IDs to actual disks by
looking for them in /dev/disks/by-uuid.
So you see why this is not a very easy solution.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
ut
> >> our code base?
>
> Thiago Macieira (7 October 2018 20:39) wrote:
> > For example, I have ~/src as a bind-mount to ~/dev/src. That means
> >
> > ~/src/qt/qt5/qtbase/src/corelib/global/qglobal.h
> > ~/dev/src/qt/qt5/qtbase/src/corelib/global/qgloba
.
Not that it would stop *another* header from the older installation from
getting included, though.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development
g stupid/
> trivial.
Most Linux distributions or possibly OpenSSH upstream have begun disabling
older ciphers by default. Our Gerrit server uses an old version of JGit, which
uses old ciphers. You need to turn something back on. See Konstantin's reply
for a suggestion on which one.
-
the headers.
The pkg-config files and the libtool files are generated by qmake itself.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-pro
x27;m unsure if this
> is allowed.
De-inlining is binary and source compatible, so long as you accept that the
old code that did inline the function continues to do what it used o do.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open S
On Wednesday, 24 October 2018 22:52:20 PDT Ulf Hermann wrote:
> The QUIP process follows the lazy consensus mechanism. See QUIP 2 and
> QUIP 3. Jason Hihn is not an Approver.
Approvership or maintainership are not required to state opinions.
--
Thiago Macieira - thiago.macieira (AT) int
of the text, but not to change its essence. And you don't
need to be an approver to post comments there, or give +1 and -1 for that
matter.
I don't know of any contributions of code that Jason H may have made,
nonetheless his email deserves to be read and answered.
--
Thiago Macieir
utors can participate.
> Especially for something as big and divisive
That's why the QtCS consensus are not decisions of the Qt Project. The
decision is left to the mailing list. It is a good indication of support,
however.
The instruction that came out of it was to write the text so the decisio
note point 3 of RFC 7282[1], which describes
IETF's Consensus mechanism:
Rough consensus is achieved when all issues are addressed, but not
necessarily accommodated
[1] https://tools.ietf.org/html/rfc7282
--
Thiago Macieira - thiago.macieira (AT) intel.com
r being of such
> a jurisdiction I am accustomed to having responsible speech being
> permitted. You are correct that no one has to listen, but I have the right
> to express it.
You have the right to express it, but that does not imply the Qt Project has
the obligation to convey it.
--
Thiago Ma
Specifically, the CoC should not be used to discriminate
against one's political views any more than on another's sexual orientations.
And what you do on your private time is your own business.
[1] https://www.mozilla.org/en-US/about/governance/policies/participation/
--
Thiago Macie
and the resulting output was compiled
4) your definition contains an export macro:
class MY_LIBRARY_EXPORT MyLibrary :
5) said macro is __declspec(dllexport) when compiling the library and
__declspec(dllimport) when linking the library. This is "Windows DLL Basics"
and you
a problem, but I'm thinking I should pay
attention to more regular things that are well-done.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Developm
n all the content
that gets shown there is now contribution to the Qt Community and under the
CoC, just like the requirement to write in English.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_
x27;ve been successful at it. Would be nice to research.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
ot qualified to
judge and address CoC violations.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
ace and why the judgment on such situations is very subjective, best left to
humans, not to a script. And the deliberations should not be in a public
forum, like a GitHub issue.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_
e ones about the buildsystem, for a recent example.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/m
rojects - it is not a hypothetical.
We prevent this scenario by having sensible people in the CoC Committee, who
will address the problem appropriately.
And will remind the person posting the complaint of the story of the boy who
cried "wolf".
--
Thiago Macieira - thiago.macieira (AT
pinion of what it is meant to say
has more weight.
So I don't think this is a danger.
> Yes, indeed, is the text good? This has to be analyzed: in depth. And I
> would still probably avoid using hers.
And personally I'm leaning in favour of KDE's.
--
Thiago Macieira -
ement, but not with
> invoking the Covenant in its current form.
Please also note that the attack against meritocracy is more nuanced than it
appears at first sight. I don't have more information on this -- I will go
inform myself about it -- so until the
I said previously, I agree we should work together on a better version.
> I guess Qt people could do it.
I would rather we not write a text ourselves, but find something we're
comfortable with. That would be an extreme effort whose resources could be
best used elsewhere.
If the
101 - 200 of 6737 matches
Mail list logo
