+1 for this.
I met with this non-fast-forward case today. Sometimes, when people are
mirroring a git repo, and "git push --mirror" doesn't work well for some
reason. Then "git push --all" is a second choice, and this non-fast-forward
will break "git push --all". Better to warn of those force pu
On Monday 13 of May 2013 11:10:45 Oswald Buddenhagen wrote:
> On Thu, May 09, 2013 at 12:39:03AM +0200, Jaroslaw Staniek wrote:
> > Given that a new port was born[1] I'd like to ask for possibility of
> > creating wip/tizen branches in the main Qt 5 repos.
>
> please specify:
> - the repositories
Hi,
I had a closer look at the installed cmake files.
The ConfigVersion.cmake files only check the version number. This is in many
cases good enough.
Additionally they should check that the 32/64bit-ness of the installed libs
and the searching project is the same, so that for a 64bit project on
So complicating...just to not do it the proven way :)
>>Anyhow, this opens the problem of if / how we should expose the "internal
widget" used to represent those actions. As you say there are certain bits
of QAction's API that are currently available in QToolButton's one.
>That would basically mea
Hi all!
There are first new installers available in
http://download.qt-project.org/snapshots/qt/5.1/5.1.0-beta1/backups/2013-05-13-31/
Some installers are missing but those should be available soon. We are really
close to beta release so please test those and inform us immediately if you
find so
On Thu, May 09, 2013 at 12:39:03AM +0200, Jaroslaw Staniek wrote:
> Given that a new port was born[1] I'd like to ask for possibility of
> creating wip/tizen branches in the main Qt 5 repos.
>
please specify:
- the repositories
- the base branch
- the envisioned mode of operation (short-cut review
