Hi,
Am 22/04/2013 03:14, schrieb Thiago Macieira:
My server just let me know:
From git://gitorious.org/qt/qtbase
60fbb00..c5a3cfa dev- dev
1f3a67e..f78842a stable - stable
! [rejected]winrt - winrt (non-fast-forward)
PLEASE let the mailing list know
At 22/04/2013 03:14, from Thiago Macieira:
My server just let me know:
From git://gitorious.org/qt/qtbase
60fbb00..c5a3cfa dev - dev
1f3a67e..f78842a stable - stable
! [rejected] winrt - winrt (non-fast-forward)
PLEASE let the mailing list know every time
+1
This would make quick code browsing much easier; Gitorious' interface is rather
cumbersome.
--
Jake Petroules
Chief Technology Officer
Petroules Corporation · www.petroules.com
Email: jake.petrou...@petroules.com
On Apr 22, 2013, at 3:44 AM, Qi Liang liang...@digia.com wrote:
At
On Sun, Apr 21, 2013 at 06:14:08PM -0700, Thiago Macieira wrote:
My server just let me know:
From git://gitorious.org/qt/qtbase
60fbb00..c5a3cfa dev- dev
1f3a67e..f78842a stable - stable
! [rejected]winrt - winrt (non-fast-forward)
PLEASE let the
On segunda-feira, 22 de abril de 2013 07.44.31, Qi Liang wrote:
Looks like the sync script(s) is running on your server(from codereview to
gitorious)?
No, this is no the codereview-gitorious sync. This is just updating the
repositories so the statistics script can run.
--
Thiago Macieira -
On segunda-feira, 22 de abril de 2013 10.15.43, Oswald Buddenhagen wrote:
why exactly would you care? everyone working on the respective branch is
somehow involved into the rebase process. everyone else doesn't need to
care/can reset --hard if they actually have a checkout.
Because everyone
On Mon, Apr 22, 2013 at 07:16:22AM -0700, Thiago Macieira wrote:
On segunda-feira, 22 de abril de 2013 10.15.43, Oswald Buddenhagen wrote:
why exactly would you care? everyone working on the respective branch is
somehow involved into the rebase process. everyone else doesn't need to
On segunda-feira, 22 de abril de 2013 16.25.30, Oswald Buddenhagen wrote:
as far as i'm concerned, the push policy for all non-mainline branches
(in particular those without a CI) is entirely up to the discretion of
their owners.
And where is it documented for winrt?
Anyway, I'm asking for a
On Mon, Apr 22, 2013 at 07:48:07AM -0700, Thiago Macieira wrote:
On segunda-feira, 22 de abril de 2013 16.25.30, Oswald Buddenhagen wrote:
as far as i'm concerned, the push policy for all non-mainline branches
(in particular those without a CI) is entirely up to the discretion of
their
On segunda-feira, 22 de abril de 2013 16.59.27, Oswald Buddenhagen wrote:
On Mon, Apr 22, 2013 at 07:48:07AM -0700, Thiago Macieira wrote:
On segunda-feira, 22 de abril de 2013 16.25.30, Oswald Buddenhagen wrote:
as far as i'm concerned, the push policy for all non-mainline branches
(in
On Mon, Apr 22, 2013 at 08:11:22AM -0700, Thiago Macieira wrote:
On segunda-feira, 22 de abril de 2013 16.59.27, Oswald Buddenhagen wrote:
On Mon, Apr 22, 2013 at 07:48:07AM -0700, Thiago Macieira wrote:
On segunda-feira, 22 de abril de 2013 16.25.30, Oswald Buddenhagen wrote:
as far as
On segunda-feira, 22 de abril de 2013 17.44.41, Oswald Buddenhagen wrote:
On Mon, Apr 22, 2013 at 08:11:22AM -0700, Thiago Macieira wrote:
On segunda-feira, 22 de abril de 2013 16.59.27, Oswald Buddenhagen wrote:
And where is it documented for winrt?
why should it be?
Because
I've pushed a review to Gerrit providing support for TLS supplemental data and
TLS extensions via a new pair of classes and APIs added to QSslSocket (six new
setters/accessors and four new signals).
Review available here:
https://codereview.qt-project.org/#q,54364,n,z
Wiki topic updated to
13 matches
Mail list logo
