On Sat, Feb 16, 2013 at 1:24 PM, Mohsen Akhlaghi wrote:
> How can I contact John Layt? I’ve sent many emails to him regarding the
> calendar globalization but no answer.
>
> Hey John do you see me? echo…
You can try IRC if he's online there: jlayt (if i recall correct)
___
Hello,
it happens quite regularly that people do a rebase and in addition do
changes in the same push. It looks like this:
git pull --rebase # or cherry-pick or whatever you do
# do some changes
git commit -a --amend
git push gerrit HEAD:refs/for/some_branch
and it makes the diff between patch
Hi Andrea, Simon,
thank you for your responses.
Please don't get me wrong, I'd rather avoid adding new layers,
but in this case, we started to consider a new module because (libjingle is
basically a big collection of libraries)
we didn't want to pollute Qtwebkit project with lots of dependencies
On Wed, Feb 20, 2013 at 3:03 AM, Olivier Goffart wrote:
> Normally, one should read that page before reporting a bug:
> http://qt-project.org/wiki/ReportingBugsInQt
> Maybe that page should be linked from the "Create Issue" form.
It would also be a good idea to have a reminder on the Create Issue
On terça-feira, 19 de fevereiro de 2013 19.29.50, Turunen Tuukka wrote:
> Hi Thiago,
>
> Due to the way earlier releases are done it is not possible to have
> perfectly clean history. This has been discussed in December and after the
> different options were analysed it was seen the best one to do
To web@:
The download page does not list at all the split packages, even though they're
the official way of building Qt from sources. I'd like to request that the
webpage be modified to list the split sources first and foremost.
Linking to the grouped sources should come after a notice saying "
Hi Thiago,
Due to the way earlier releases are done it is not possible to have perfectly
clean history. This has been discussed in December and after the different
options were analysed it was seen the best one to do as it now is. End result
is the same, we have 4.6.5 and 4.7.6 releases availa
On terça-feira, 19 de fevereiro de 2013 16.42.44, Turunen Tuukka wrote:
> Hi Thiago,
>
> The whole idea of 4.6.5 and 4.7.6 is to unfork these and unify. It has
> never been about making a Digia specific release. We have no intention to
> make any Digia specific 4.6 and 4.7 release - quite the oppos
Fredag 15. februar 2013 12.47.49 skrev Shaw Andy:
> Hi,
>
> Before the transition to Qt being developed in the open via open governance,
> the Qt Support team back in Trolltech and later Nokia, would prioritize the
> bugs that were created, or at least handled, by them. Typically these would
> be
On Tuesday 19 February 2013 16:26:31 Mitch Curtis wrote:
> On 02/19/2013 03:33 PM, Motyka Rafal wrote:
> > Hello,
> >
> > In order to address some of the recent questions about error management,
> > and to improve the quality of bug reports, I want to suggest using the
> > following template:
> >
Hi Thiago,
The whole idea of 4.6.5 and 4.7.6 is to unfork these and unify. It has
never been about making a Digia specific release. We have no intention to
make any Digia specific 4.6 and 4.7 release - quite the opposite - we wish
to unify those releases that have been done earlier (and even then
On sexta-feira, 21 de dezembro de 2012 16.11.08, Salovaara Akseli wrote:
> We have created Qt 4.6.5 and 4.7.6 release candidates that bring the
> following changes over the previous ones in their series:
$ ncftpls ftp://ftp.qt-project.org/qt/source/*4.7.*.tar.gz
qt-everywhere-opensource-src-4.7.0.
On 02/19/2013 03:33 PM, Motyka Rafal wrote:
> Hello,
>
> In order to address some of the recent questions about error management,
> and to improve the quality of bug reports, I want to suggest using the
> following template:
>
> ==
> PACKAGE NAME:
> <
Hello,
In order to address some of the recent questions about error management, and to
improve the quality of bug reports, I want to suggest using the following
template:
==
PACKAGE NAME:
< e.g. qt-windows-opensource-5.0.1-mingw47_32-x86-offline-2
Hi All,
I am testing my Qt built libraries with a simple test
application, which basically creates a window with a button.
Its as shown
/ButtonApp.c*/
#include
extern "C" void WebKitTestApp(void *pdata)
{
int argv=1;
char *args[]={"WebKit
15 matches
Mail list logo
