Albert Astals Cid wrote:
> I personally feel the loss of "email gets sent to kde-frameworks-devel on MR"
> is a problem.
And I find that the lack of being able to interact with tickets via email a big
handicap.
This is also the review system now used by KDevelop where you can no longer
submit
On Mon, Aug 12, 2019, 18:46 Ben Cooksley wrote:
> On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca Cintora
> wrote:
> >
> > Could we use sysadmin/repo-metadata to know which branch is stable and
> therefore should be protected and trigger the hooks for closing bugs, etc?
>
> Unfortunately that only
Could we use sysadmin/repo-metadata to know which branch is stable and
therefore should be protected and trigger the hooks for closing bugs, etc?
On Mon, Aug 12, 2019, 17:39 Ben Cooksley wrote:
> On Mon, Aug 12, 2019 at 6:24 PM Kevin Ottens wrote:
> >
> > Hello,
>
> Hi Kevin,
>
> >
> > On
On Fri, Aug 16, 2019 at 6:30 AM Christoph Cullmann
wrote:
>
> Hi,
Hi Christoph,
>
> >> perhaps this would be some good BoF at Akademy:
> >>
> >> What is needed to move frameworks development to invent.kde.org.
> >>
> >> (I assume we want to do that some when in the future anyways)
> >
> > At
Hi,
perhaps this would be some good BoF at Akademy:
What is needed to move frameworks development to invent.kde.org.
(I assume we want to do that some when in the future anyways)
At this point my planning expected that Frameworks would move when the
rest of KDE moves (which will likely be a
On Wed, Aug 14, 2019 at 8:25 AM Albert Astals Cid wrote:
>
> El dimarts, 13 d’agost de 2019, a les 13:26:43 CEST, Harald Sitter va
> escriure:
> > On Tue, Aug 13, 2019 at 12:54 PM Ben Cooksley wrote:
> > >
> > > On Mon, Aug 12, 2019 at 11:48 PM David Faure wrote:
> > > >
> > > > On lundi 12
On Wed, Aug 14, 2019 at 9:07 AM Christoph Cullmann
wrote:
>
> Hi,
>
> >> > Unfortunately the problem isn't with Frameworks, Applications and
> >> > Plasma - they're easy to handle and their naming can be scripted
> >> > without too much trouble.
> >> > The problem lies with Extragear, which has a
Hi,
> Unfortunately the problem isn't with Frameworks, Applications and
> Plasma - they're easy to handle and their naming can be scripted
> without too much trouble.
> The problem lies with Extragear, which has a large number of projects,
> all of which have different rules for what a stable
El dimarts, 13 d’agost de 2019, a les 13:26:43 CEST, Harald Sitter va escriure:
> On Tue, Aug 13, 2019 at 12:54 PM Ben Cooksley wrote:
> >
> > On Mon, Aug 12, 2019 at 11:48 PM David Faure wrote:
> > >
> > > On lundi 12 août 2019 13:04:29 CEST Ben Cooksley wrote:
> > > > On Mon, Aug 12, 2019 at
On Tue, Aug 13, 2019 at 11:27 PM Harald Sitter wrote:
>
> On Tue, Aug 13, 2019 at 12:54 PM Ben Cooksley wrote:
> >
> > On Mon, Aug 12, 2019 at 11:48 PM David Faure wrote:
> > >
> > > On lundi 12 août 2019 13:04:29 CEST Ben Cooksley wrote:
> > > > On Mon, Aug 12, 2019 at 10:54 PM Albert Vaca
On Tue, Aug 13, 2019 at 12:54 PM Ben Cooksley wrote:
>
> On Mon, Aug 12, 2019 at 11:48 PM David Faure wrote:
> >
> > On lundi 12 août 2019 13:04:29 CEST Ben Cooksley wrote:
> > > On Mon, Aug 12, 2019 at 10:54 PM Albert Vaca Cintora
> > >
> > > wrote:
> > > > On Mon, Aug 12, 2019, 18:46 Ben
On Mon, Aug 12, 2019 at 11:48 PM David Faure wrote:
>
> On lundi 12 août 2019 13:04:29 CEST Ben Cooksley wrote:
> > On Mon, Aug 12, 2019 at 10:54 PM Albert Vaca Cintora
> >
> > wrote:
> > > On Mon, Aug 12, 2019, 18:46 Ben Cooksley wrote:
> > >> On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca
Hello,
On Monday, 12 August 2019 13:48:46 CEST David Faure wrote:
> In any case, we should be able to make a list of stable branches,
> especially if we can use wildcards like Applications/*.
And that's kind of the way GitLab works IIUC. By default only master is
protected, but you can set
El dilluns, 12 d’agost de 2019, a les 11:38:50 CEST, Ben Cooksley va escriure:
> Those familiar to Git will be aware that it is very much possible to
> limit the scope of hooks like our Notification hooks, while still
> allowing them to be caught when entering branches that are subject to
>
On lundi 12 août 2019 13:04:29 CEST Ben Cooksley wrote:
> On Mon, Aug 12, 2019 at 10:54 PM Albert Vaca Cintora
>
> wrote:
> > On Mon, Aug 12, 2019, 18:46 Ben Cooksley wrote:
> >> On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca Cintora
> >>
> >> wrote:
> >> > Could we use sysadmin/repo-metadata
On Mon, Aug 12, 2019 at 10:54 PM Albert Vaca Cintora
wrote:
>
>
> On Mon, Aug 12, 2019, 18:46 Ben Cooksley wrote:
>>
>> On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca Cintora
>> wrote:
>> >
>> > Could we use sysadmin/repo-metadata to know which branch is stable and
>> > therefore should be
On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca Cintora
wrote:
>
> Could we use sysadmin/repo-metadata to know which branch is stable and
> therefore should be protected and trigger the hooks for closing bugs, etc?
Unfortunately that only tells us what the current stable branch is -
it doesn't let
On Mon, Aug 12, 2019 at 6:24 PM Kevin Ottens wrote:
>
> Hello,
Hi Kevin,
>
> On Sunday, 11 August 2019 22:14:19 CEST Albert Astals Cid wrote:
> > With phabricator you can do a "force push" to your review[1], with gitlab
> > you can not[2].
> > [...]
> > [2] without having your own fork of a
Hello,
On Sunday, 11 August 2019 22:14:19 CEST Albert Astals Cid wrote:
> With phabricator you can do a "force push" to your review[1], with gitlab
> you can not[2].
> [...]
> [2] without having your own fork of a repository, that is annoying for
> various reasons
I'm genuinely surprised about
On Mon, Aug 12, 2019 at 12:23 AM David Faure wrote:
>
> On dimanche 11 août 2019 22:14:19 CEST Albert Astals Cid wrote:
> > without having your own fork of a repository, that is annoying for various
> > reasons
>
> If creating a fork can be scripted, then that could be a fallback solution
> (to
On dimanche 11 août 2019 22:14:19 CEST Albert Astals Cid wrote:
> without having your own fork of a repository, that is annoying for various
> reasons
If creating a fork can be scripted, then that could be a fallback solution
(to the problem of "committing everywhere" like some of us do).
--
On dimanche 11 août 2019 12:33:19 CEST Christoph Cullmann wrote:
> Hi,
>
> is it possible to move individual framework modules over to
> invent.kde.org or will that be
> done at once somewhen in the future?
>
> Would be interested to move syntax-highlighting and ktexteditor if that
> is
El diumenge, 11 d’agost de 2019, a les 21:00:13 CEST, Ben Cooksley va escriure:
> On Mon, Aug 12, 2019 at 2:53 AM Albert Astals Cid wrote:
> >
> > El diumenge, 11 d’agost de 2019, a les 12:33:19 CEST, Christoph Cullmann va
> > escriure:
> > > Hi,
> > >
> > > is it possible to move individual
On Mon, Aug 12, 2019 at 2:53 AM Albert Astals Cid wrote:
>
> El diumenge, 11 d’agost de 2019, a les 12:33:19 CEST, Christoph Cullmann va
> escriure:
> > Hi,
> >
> > is it possible to move individual framework modules over to
> > invent.kde.org or will that be
> > done at once somewhen in the
On 2019-08-11 16:53, Albert Astals Cid wrote:
El diumenge, 11 d’agost de 2019, a les 12:33:19 CEST, Christoph
Cullmann va escriure:
Hi,
is it possible to move individual framework modules over to
invent.kde.org or will that be
done at once somewhen in the future?
Seems kde-frameworks-devel
El diumenge, 11 d’agost de 2019, a les 12:33:19 CEST, Christoph Cullmann va
escriure:
> Hi,
>
> is it possible to move individual framework modules over to
> invent.kde.org or will that be
> done at once somewhen in the future?
Seems kde-frameworks-devel would be a better list to ask about
Hi,
is it possible to move individual framework modules over to
invent.kde.org or will that be
done at once somewhen in the future?
Would be interested to move syntax-highlighting and ktexteditor if that
is possible.
But if that shall be done as bulk in the future I can wait ;=)
Greetings
27 matches
Mail list logo
