On Feb 17, 2014 9:14 AM, "Paul Gideon Dann" wrote:
>
> On Monday 17 Feb 2014 08:03:24 Alexander Dymo wrote:
>
> > > That said, last time I tried it was a resource consumer monster, has
that
>
> > > been fixed? Is it going to scale KDE size?
>
> >
>
> > It's a Rails app. Those tend to use more reso
On Thursday 20 Feb 2014 21:40:25 Ben Cooksley wrote:
> >> I tried working with github for a project, using a workflow of reviewing
> >> each commit. I personally really disliked it for creating a merge commit
> >> for each commit, that just clutters up the history (try looking at any
> >> github pr
On Thu, Feb 20, 2014 at 5:26 AM, Àlex Fiestas wrote:
> On Tuesday 18 February 2014 13:45:41 Frederik Gladhorn wrote:
>> On Saturday 15. February 2014 15.30.54 Àlex Fiestas wrote:
>> > On Friday 14 February 2014 22:52:04 Jeff Mitchell wrote:
>> > > This email serves two purposes: one, to inform the
On Tuesday 18 February 2014 13:45:41 Frederik Gladhorn wrote:
> On Saturday 15. February 2014 15.30.54 Àlex Fiestas wrote:
> > On Friday 14 February 2014 22:52:04 Jeff Mitchell wrote:
> > > This email serves two purposes: one, to inform the community of the
> > > direction we would like to go with
On Sunday 16 February 2014 22:10:38 Ben Cooksley wrote:
> On Sun, Feb 16, 2014 at 3:30 AM, Àlex Fiestas wrote:
> > On Friday 14 February 2014 22:52:04 Jeff Mitchell wrote:
> >> This email serves two purposes: one, to inform the community of the
> >> direction we would like to go with KDE's Git hos
On 18 Feb 2014, at 7:45, Frederik Gladhorn wrote:
I tried working with github for a project, using a workflow of
reviewing each commit.
I personally really disliked it for creating a merge commit for each
commit, that just
clutters up the history (try looking at any github project with a few
co
On 18 Feb 2014, at 11:22, Martin Klapetek wrote:
Generally speaking, Gerrit needs to "own" repositories. Would this
require
some sort of thing like RB hosting the Git repos?
Sort of, it would need its own clone of the repos, which is moreless
the
case right now anyway right? But I imagine i
On Tue, Feb 18, 2014 at 5:19 PM, Jeff Mitchell wrote:
> On 18 Feb 2014, at 8:02, Martin Klapetek wrote:
>
>> Fwiw, the Review Board guys are working on a push-based review system,
>> bascially a gerrit with RB interface. This is a set of extension scripts
>> usable with RB 2.0, which brings many
On 18 Feb 2014, at 8:02, Martin Klapetek wrote:
Fwiw, the Review Board guys are working on a push-based review system,
bascially a gerrit with RB interface. This is a set of extension
scripts
usable with RB 2.0, which brings many other features as well, you can
watch
a video of it here: http://
On 17 Feb 2014, at 9:14, Paul Gideon Dann wrote:
On Monday 17 Feb 2014 08:03:24 Alexander Dymo wrote:
That said, last time I tried it was a resource consumer monster,
has that
been fixed? Is it going to scale KDE size?
It's a Rails app. Those tend to use more resources. But deploying
with
On Tue, Feb 18, 2014 at 1:45 PM, Frederik Gladhorn wrote:
>
>
> I tried working with github for a project, using a workflow of reviewing
> each commit. I personally really disliked it for creating a merge commit
> for each commit, that just clutters up the history (try looking at any
> github pro
On Saturday 15. February 2014 15.30.54 Àlex Fiestas wrote:
> On Friday 14 February 2014 22:52:04 Jeff Mitchell wrote:
> > This email serves two purposes: one, to inform the community of the
> > direction we would like to go with KDE's Git hosting and request
> > feedback; two, to ask for volunteer
On 02/15/2014 05:52 AM, Jeff Mitchell wrote:
This email serves two purposes: one, to inform the community of the
direction we would like to go with KDE's Git hosting and request
feedback;
+1 :)
two, to ask for volunteer projects that are willing to act as
crash test dummies for the new system
On Monday 17 Feb 2014 08:03:24 Alexander Dymo wrote:
> > That said, last time I tried it was a resource consumer monster,
has that
> > been fixed? Is it going to scale KDE size?
>
> It's a Rails app. Those tend to use more resources. But deploying
with Ruby
> 2.1 might have a huge difference per
That said, last time I tried it was a resource consumer monster, has that been
fixed? Is it going to scale KDE size?
It's a Rails app. Those tend to use more resources. But deploying with Ruby 2.1
might have a huge difference performance-wise.
___
kde
On Sun, Feb 16, 2014 at 3:30 AM, Àlex Fiestas wrote:
> On Friday 14 February 2014 22:52:04 Jeff Mitchell wrote:
>> This email serves two purposes: one, to inform the community of the
>> direction we would like to go with KDE's Git hosting and request
>> feedback; two, to ask for volunteer projects
On Sun, Feb 16, 2014 at 12:28 AM, Albert Astals Cid wrote:
> El Divendres, 14 de febrer de 2014, a les 22:52:04, Jeff Mitchell va escriure:
>> (Sending from the proper account this time)
>>
>> Hello KDE Community,
>>
>> Several years ago when transitioning to Git the sysadmins evaluated
>> several
On Sat, Feb 15, 2014 at 11:55 PM, Aaron J. Seigo wrote:
> On Friday, February 14, 2014 22:52:04 Jeff Mitchell wrote:
>> However, in the intervening years, GitLab (https://www.gitlab.com/) has
>
> Playing around with the demo a bit this morning, there are a number of
> benefits
> I see, most of wh
On Friday 14 February 2014 22:52:04 Jeff Mitchell wrote:
> This email serves two purposes: one, to inform the community of the
> direction we would like to go with KDE's Git hosting and request
> feedback; two, to ask for volunteer projects that are willing to act as
> crash test dummies for the ne
Le 15/02/2014 11:55, Aaron J. Seigo a écrit :
This email serves two purposes: one, to inform the community of the
>direction we would like to go with KDE's Git hosting and request
>feedback; two, to ask for volunteer projects that are willing to act as
>crash test dummies for the new system, help
Hello KDE Community,
Several years ago when transitioning to Git the sysadmins evaluated
several possible options, including GitLab, Gitorious, Gitolite, and
Gerrit. At the time, GitLab was quite immature in terms of code,
community, and documentation. After evaluating options, we chose
Gitol
El Divendres, 14 de febrer de 2014, a les 22:52:04, Jeff Mitchell va escriure:
> (Sending from the proper account this time)
>
> Hello KDE Community,
>
> Several years ago when transitioning to Git the sysadmins evaluated
> several possible options, including GitLab, Gitorious, Gitolite, and
> Ge
On Friday, February 14, 2014 22:52:04 Jeff Mitchell wrote:
> However, in the intervening years, GitLab (https://www.gitlab.com/) has
Playing around with the demo a bit this morning, there are a number of benefits
I see, most of which you already mentioned. The big one for me is the
integration;
(Sending from the proper account this time)
Hello KDE Community,
Several years ago when transitioning to Git the sysadmins evaluated
several possible options, including GitLab, Gitorious, Gitolite, and
Gerrit. At the time, GitLab was quite immature in terms of code,
community, and documentati
24 matches
Mail list logo
