---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109503/
---
(Updated April 13, 2013, 9:31 p.m.)
Status
--
This change has been ma
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109503/#review31006
---
This review has been submitted with commit
b7e1f3decc425c258e1
On Mon, Mar 18, 2013 at 4:12 AM, David Faure wrote:
> On Sunday 17 March 2013 13:51:39 Stephen Kelly wrote:
>> Ben Cooksley wrote:
>> > Long term we either need:
>> > 1) A commitment from the Qt project to make keeping qt5.git updated a
>> > high priority (block all new commits from entering any s
On Sunday 17 March 2013 13:51:39 Stephen Kelly wrote:
> Ben Cooksley wrote:
> > Long term we either need:
> > 1) A commitment from the Qt project to make keeping qt5.git updated a
> > high priority (block all new commits from entering any submodule until
> > the issues in question are fixed for ins
Ben Cooksley wrote:
> Long term we either need:
> 1) A commitment from the Qt project to make keeping qt5.git updated a
> high priority (block all new commits from entering any submodule until
> the issues in question are fixed for instance) or
> 2) We need to decide to adopt either qt5.git or indi
On Sun, Mar 17, 2013 at 10:35 PM, David Faure wrote:
> On Sunday 17 March 2013 20:58:08 Ben Cooksley wrote:
>> On Sun, Mar 17, 2013 at 12:59 AM, Stephen Kelly wrote:
>> > Ben Cooksley wrote:
>> >> I tried the command invocation:
>> >> git submodule foreach 'git fetch; git reset --hard origin/dev
On Sunday 17 March 2013 20:58:08 Ben Cooksley wrote:
> On Sun, Mar 17, 2013 at 12:59 AM, Stephen Kelly wrote:
> > Ben Cooksley wrote:
> >> I tried the command invocation:
> >> git submodule foreach 'git fetch; git reset --hard origin/dev || git
> >> reset --hard origin/master || true'
> >>
> >> W
On Sun, Mar 17, 2013 at 12:59 AM, Stephen Kelly wrote:
> Ben Cooksley wrote:
>
>> I tried the command invocation:
>> git submodule foreach 'git fetch; git reset --hard origin/dev || git
>> reset --hard origin/master || true'
>>
>> Which does do the job. However, as feared Jenkins is far too clever
Ben Cooksley wrote:
> I tried the command invocation:
> git submodule foreach 'git fetch; git reset --hard origin/dev || git
> reset --hard origin/master || true'
>
> Which does do the job. However, as feared Jenkins is far too clever
> and overwrites that completely, checking out the directories
On Sun, Mar 17, 2013 at 12:29 AM, Stephen Kelly wrote:
> Ben Cooksley wrote:
>
>> On Sun, Mar 17, 2013 at 12:23 AM, Stephen Kelly
>> wrote:
>>> Stephen Kelly wrote:
>>>
Ben Cooksley wrote:
> In theory, however Jenkins itself does Git handling for part of the
> process and that may ve
Ben Cooksley wrote:
> On Sun, Mar 17, 2013 at 12:23 AM, Stephen Kelly
> wrote:
>> Stephen Kelly wrote:
>>
>>> Ben Cooksley wrote:
In theory, however Jenkins itself does Git handling for part of the
process and that may very well override our invocation of that.
In any case, gi
On Sun, Mar 17, 2013 at 12:23 AM, Stephen Kelly wrote:
> Stephen Kelly wrote:
>
>> Ben Cooksley wrote:
>>> In theory, however Jenkins itself does Git handling for part of the
>>> process and that may very well override our invocation of that.
>>>
>>> In any case, git spits out the following if I r
Stephen Kelly wrote:
> Ben Cooksley wrote:
>> In theory, however Jenkins itself does Git handling for part of the
>> process and that may very well override our invocation of that.
>>
>> In any case, git spits out the following if I run that for each
>> submodule:
>>
>> You are not currently on
Ben Cooksley wrote:
> In theory, however Jenkins itself does Git handling for part of the
> process and that may very well override our invocation of that.
>
> In any case, git spits out the following if I run that for each submodule:
>
> You are not currently on a branch, so I cannot use any
> '
> On March 15, 2013, 5:07 p.m., Stephen Kelly wrote:
> > The problem is that build.kde.org uses qt5.git, which does not yet have
> > that commit. Actually qt5.git hasn't been updated in 6 weeks:
> > https://codereview.qt-project.org/#change,46445
> >
> > If b.k.o can be updated to use the dev
> On March 15, 2013, 5:07 p.m., Stephen Kelly wrote:
> > The problem is that build.kde.org uses qt5.git, which does not yet have
> > that commit. Actually qt5.git hasn't been updated in 6 weeks:
> > https://codereview.qt-project.org/#change,46445
> >
> > If b.k.o can be updated to use the dev
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109503/
---
(Updated March 15, 2013, 8:42 p.m.)
Status
--
This change has been di
> On March 15, 2013, 5:07 p.m., Stephen Kelly wrote:
> > The problem is that build.kde.org uses qt5.git, which does not yet have
> > that commit. Actually qt5.git hasn't been updated in 6 weeks:
> > https://codereview.qt-project.org/#change,46445
> >
> > If b.k.o can be updated to use the dev
> On March 15, 2013, 5:07 p.m., Stephen Kelly wrote:
> > The problem is that build.kde.org uses qt5.git, which does not yet have
> > that commit. Actually qt5.git hasn't been updated in 6 weeks:
> > https://codereview.qt-project.org/#change,46445
> >
> > If b.k.o can be updated to use the dev
> On March 15, 2013, 5:07 p.m., Stephen Kelly wrote:
> > The problem is that build.kde.org uses qt5.git, which does not yet have
> > that commit. Actually qt5.git hasn't been updated in 6 weeks:
> > https://codereview.qt-project.org/#change,46445
> >
> > If b.k.o can be updated to use the dev
> On March 15, 2013, 5:07 p.m., Stephen Kelly wrote:
> > The problem is that build.kde.org uses qt5.git, which does not yet have
> > that commit. Actually qt5.git hasn't been updated in 6 weeks:
> > https://codereview.qt-project.org/#change,46445
> >
> > If b.k.o can be updated to use the dev
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109503/#review29284
---
The problem is that build.kde.org uses qt5.git, which does not
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109503/
---
Review request for KDE Frameworks.
Description
---
34a3f2cd442ff1396e
23 matches
Mail list logo
