[GitHub] mesos pull request #122: docs: frameworks list: use correct URL for storm-me...

GitHub user erikdw opened a pull request: https://github.com/apache/mesos/pull/122 docs: frameworks list: use correct URL for storm-mesos framework You can merge this pull request into a Git repository by running: $ git pull https://github.com/erikdw/mesos

[GitHub] mesos pull request #121: Addition of ndustrial.io to Mesos User List

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/121 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #121: Addition of ndustrial.io to Mesos User List

GitHub user jrcrawfo opened a pull request: https://github.com/apache/mesos/pull/121 Addition of ndustrial.io to Mesos User List You can merge this pull request into a Git repository by running: $ git pull https://github.com/jrcrawfo/mesos patch-2 Alternatively you can

[GitHub] mesos pull request #119: Added gigawatt.io to "powered by".

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/119 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #120: Add Opera to "Powered by Mesos" list

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/120 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #120: Add Opera to "Powered by Mesos" list

GitHub user mlowicki opened a pull request: https://github.com/apache/mesos/pull/120 Add Opera to "Powered by Mesos" list You can merge this pull request into a Git repository by running: $ git pull https://github.com/mlowicki/mesos patch-1 Alternatively you can review and

[GitHub] mesos pull request #119: Added gigawatt.io to "powered by".

GitHub user jaytaylor opened a pull request: https://github.com/apache/mesos/pull/119 Added gigawatt.io to "powered by". You can merge this pull request into a Git repository by running: $ git pull https://github.com/GigawattIO/mesos jay/gigawattio Alternatively you can

[GitHub] mesos pull request #111: Have maven run in batch mode

Github user drcrallen closed the pull request at: https://github.com/apache/mesos/pull/111 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: [GitHub] mesos pull request #127: added DevOps category and Vamp

Pushed. On Tue, Jul 5, 2016 at 7:10 PM, haosdent wrote: > Github user haosdent commented on a diff in the pull request: > > https://github.com/apache/mesos/pull/127#discussion_r69601291 > > --- Diff: docs/frameworks.md --- > @@ -4,6 +4,10 @@ layout:

[GitHub] mesos pull request #127: added DevOps category and Vamp

Github user haosdent commented on a diff in the pull request: https://github.com/apache/mesos/pull/127#discussion_r69601291 --- Diff: docs/frameworks.md --- @@ -4,6 +4,10 @@ layout: documentation --- # Software Projects Built on Mesos +## DevOps tooling +

[GitHub] mesos pull request #127: added DevOps category and Vamp

Github user haosdent commented on a diff in the pull request: https://github.com/apache/mesos/pull/127#discussion_r69599122 --- Diff: docs/frameworks.md --- @@ -4,6 +4,10 @@ layout: documentation --- # Software Projects Built on Mesos +## DevOps tooling +

[GitHub] mesos pull request #127: added DevOps category and Vamp

GitHub user gggina opened a pull request: https://github.com/apache/mesos/pull/127 added DevOps category and Vamp You can merge this pull request into a Git repository by running: $ git pull https://github.com/gggina/mesos patch-1 Alternatively you can review and apply these

[GitHub] mesos pull request #126: Question : mesos networking

GitHub user angry-tony opened a pull request: https://github.com/apache/mesos/pull/126 Question : mesos networking I am wondering if Mesos can offer resources from multiple network interfaces? I would like to attach multiple Network Interfaces (public eth0, private eth1) on

[GitHub] mesos pull request #116: Added self to contributors.

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/116 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #116: Added self to contributors.

GitHub user HarisChoudhary opened a pull request: https://github.com/apache/mesos/pull/116 Added self to contributors. You can merge this pull request into a Git repository by running: $ git pull https://github.com/HarisChoudhary/mesos master Alternatively you can review and

[GitHub] mesos pull request #115: Added xiaods as contributor.

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/115 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #115: Added xiaods as contributor.

GitHub user xiaods opened a pull request: https://github.com/apache/mesos/pull/115 Added xiaods as contributor. The contributors.yaml has been updated adding myself as contributor You can merge this pull request into a Git repository by running: $ git pull

[GitHub] mesos pull request #114: Added jvanz as contributor.

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/114 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #113: Added a file to test PR notifications.

GitHub user mesosprbot opened a pull request: https://github.com/apache/mesos/pull/113 Added a file to test PR notifications. You can merge this pull request into a Git repository by running: $ git pull https://github.com/artemharutyunyan/mesos master Alternatively you can

[GitHub] mesos pull request #114: Added jvanz as contributor.

GitHub user jvanz opened a pull request: https://github.com/apache/mesos/pull/114 Added jvanz as contributor. The contributors.yaml has been updated adding myself as contributor You can merge this pull request into a Git repository by running: $ git pull

[GitHub] mesos pull request: Slave/Agent rename in diagrams.

GitHub user guoger opened a pull request: https://github.com/apache/mesos/pull/109 Slave/Agent rename in diagrams. Diagrams under docs/images are renamed. Review: https://reviews.apache.org/r/47907 You can merge this pull request into a Git repository by running: $

[GitHub] mesos pull request: Slave/Agent rename in diagrams.

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/109 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request: Add Livespotting into powered-by-mesos.md

Github user jstabenow commented on the pull request: https://github.com/apache/mesos/pull/106#issuecomment-221534774 @tillt thanks :-) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request: Add CMCRC to powered-by-mesos.md

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/108 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request: Add CMCRC to powered-by-mesos.md

Github user tillt commented on the pull request: https://github.com/apache/mesos/pull/108#issuecomment-221532921 Committed as: ``` commit b33e780909561e07b377c9836c43b65117e98630 Author: Spritekin Date: Wed May 25 12:19:34 2016 +0200

[GitHub] mesos pull request: Add Livespotting into powered-by-mesos.md

Github user tillt commented on the pull request: https://github.com/apache/mesos/pull/106#issuecomment-221533453 Committed as: ``` commit 71b47658e411456df4a34491ea82bd4115f70479 Author: Jan Stabenow Date: Wed May 25 12:23:30 2016 +0200

[GitHub] mesos pull request: Add Livespotting into powered-by-mesos.md

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/106 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request: Added Teralytics to list of Mesos' users

GitHub user elbryan opened a pull request: https://github.com/apache/mesos/pull/107 Added Teralytics to list of Mesos' users You can merge this pull request into a Git repository by running: $ git pull https://github.com/elbryan/mesos teralytics-powered-by-mesos

[GitHub] mesos pull request: Added Teralytics to list of Mesos' users

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/107 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request: Add CMCRC to powered-by-mesos.md

GitHub user Spritekin opened a pull request: https://github.com/apache/mesos/pull/108 Add CMCRC to powered-by-mesos.md Please add CMCRC to the powered by mesos list. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Spritekin/mesos

[GitHub] mesos pull request: MESOS-3932 Suppressed boost auto_ptr compile w...

GitHub user frankscholten opened a pull request: https://github.com/apache/mesos/pull/104 MESOS-3932 Suppressed boost auto_ptr compile warnings. You can merge this pull request into a Git repository by running: $ git pull https://github.com/frankscholten/mesos MESOS-3932

[GitHub] mesos pull request: Changes in support of MESOS-3690

Github user haosdent commented on the pull request: https://github.com/apache/mesos/pull/75#issuecomment-219915168 @fayusohenson I copy your patch to https://reviews.apache.org/r/47510/ for review convenience. Noted that @janisz has similar patch on

[GitHub] mesos pull request: Changes in support of MESOS-3690

Github user haosdent commented on the pull request: https://github.com/apache/mesos/pull/75#issuecomment-219896230 @fayusohenson Are you still working on this? May you post it in reviewboard? https://reviews.apache.org/groups/mesos/ --- If your project is set up for it, you can

[GitHub] mesos pull request: Add 0.28.1, fix broken download link

GitHub user stain opened a pull request: https://github.com/apache/mesos/pull/97 Add 0.28.1, fix broken download link You can merge this pull request into a Git repository by running: $ git pull https://github.com/stain/mesos patch-1 Alternatively you can review and apply

[GitHub] mesos pull request: Add OVH to the Powered By Mesos list

Github user thomas-maurice commented on the pull request: https://github.com/apache/mesos/pull/98#issuecomment-214309173 :+1: --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] mesos pull request: Add OVH to the Powered By Mesos list

GitHub user kdevroede opened a pull request: https://github.com/apache/mesos/pull/98 Add OVH to the Powered By Mesos list Signed-off-by: Kevin Devroede You can merge this pull request into a Git repository by running: $ git pull

[GitHub] mesos pull request: Bugfix documentation

GitHub user albsOps opened a pull request: https://github.com/apache/mesos/pull/96 Bugfix documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/albsOps/mesos bugfix_docs Alternatively you can review and apply these

[GitHub] mesos pull request: Added Raleigh/Durham User Group

Github user haosdent commented on a diff in the pull request: https://github.com/apache/mesos/pull/95#discussion_r58294393 --- Diff: site/source/community/user-groups.html.md --- @@ -44,6 +44,7 @@ Mesos User Groups (MUGs) are responsible for organizing local meetups, hackathon

[GitHub] mesos pull request: Upgrade zookeeper to 3.4.8.

Github user vinodkone commented on the pull request: https://github.com/apache/mesos/pull/93#issuecomment-204558214 libev is committed. You can rebase it now. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

[GitHub] mesos pull request: Upgrade zookeeper to 3.4.8.

Github user chenzhiwei commented on the pull request: https://github.com/apache/mesos/pull/93#issuecomment-204145852 I found I need to rebase again if the upgrade libev patch was submitted, so let's wait for libev patch to be submitted, then I will rebase. --- If your project is set

[GitHub] mesos pull request: Upgrade zookeeper to 3.4.8.

Github user chenzhiwei commented on a diff in the pull request: https://github.com/apache/mesos/pull/93#discussion_r58131254 --- Diff: 3rdparty/Makefile.am --- @@ -51,7 +51,7 @@ EXTRA_DIST = \ EXTRA_DIST += \ $(LEVELDB).patch -# We

[GitHub] mesos pull request: Upgrade zookeeper to 3.4.8.

Github user vinodkone commented on a diff in the pull request: https://github.com/apache/mesos/pull/93#discussion_r58094904 --- Diff: 3rdparty/Makefile.am --- @@ -51,7 +51,7 @@ EXTRA_DIST = \ EXTRA_DIST += \ $(LEVELDB).patch -# We

[GitHub] mesos pull request: Added Raleigh/Durham User Group

GitHub user jrcrawfo opened a pull request: https://github.com/apache/mesos/pull/95 Added Raleigh/Durham User Group You can merge this pull request into a Git repository by running: $ git pull https://github.com/jrcrawfo/mesos patch-1 Alternatively you can review and apply

[GitHub] mesos pull request: Fixing invalid element in UI

Github user jmlvanre commented on the pull request: https://github.com/apache/mesos/pull/94#issuecomment-202839170 ``` commit 299f07a4e534f7a01a6b933d26f8935a327b5e99 Author: Sjoerd Mulder Date: Tue Mar 29 13:18:49 2016 +0200 Fixed UI

[GitHub] mesos pull request: Fixing invalid element in UI

GitHub user sjoerdmulder opened a pull request: https://github.com/apache/mesos/pull/94 Fixing invalid element in UI Caused that the table was rendered to wide. You can merge this pull request into a Git repository by running: $ git pull https://github.com/sjoerdmulder/mesos

[GitHub] mesos pull request: Fixing invalid element in UI

Github user sjoerdmulder closed the pull request at: https://github.com/apache/mesos/pull/94 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request: Fixing invalid element in UI

Github user jmlvanre commented on the pull request: https://github.com/apache/mesos/pull/94#issuecomment-202839888 @sjoerdmulder can you close this PR? I've committed to head. Thanks! --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] mesos pull request: Upgrade zookeeper to 3.4.8.

GitHub user chenzhiwei opened a pull request: https://github.com/apache/mesos/pull/93 Upgrade zookeeper to 3.4.8. You can merge this pull request into a Git repository by running: $ git pull https://github.com/chenzhiwei/mesos upgrade-zookeeper Alternatively you can review

[GitHub] mesos pull request: fixed broken 404 doc link for torque on mesos

GitHub user kensipe opened a pull request: https://github.com/apache/mesos/pull/46 fixed broken 404 doc link for torque on mesos It is unclear if Torque is an active project... I can remove the torque docs if it is preferred. However the doc links for torque resulted in a 404

[GitHub] mesos pull request: Add DataMan to the list of adopters

Github user vitan commented on the pull request: https://github.com/apache/mesos/pull/45#issuecomment-111897831 merged. thanks to @davelester --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have

[GitHub] mesos pull request: Add DataMan to the list of adopters

Github user vitan closed the pull request at: https://github.com/apache/mesos/pull/45 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request: MESOS-809: integrated into master

Github user andrewrothstein closed the pull request at: https://github.com/apache/mesos/pull/44 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] mesos pull request: Add DataMan to the list of adopters

GitHub user vitan opened a pull request: https://github.com/apache/mesos/pull/45 Add DataMan to the list of adopters We're using marathon, spark and chronos on top of the mesos 0.22.0 You can merge this pull request into a Git repository by running: $ git pull

[GitHub] mesos pull request: Add DataMan to the list of adopters

Github user davelester commented on the pull request: https://github.com/apache/mesos/pull/45#issuecomment-111747685 Thanks for adding yourself to the PoweredBy page! I just merged this into master. Could you please close this pull request? --- If your project is set up for

[GitHub] mesos pull request: Add Allegro to the list of adopters

Github user wendigo commented on the pull request: https://github.com/apache/mesos/pull/43#issuecomment-111474450 Thanks :) Closed --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request: Add Allegro to the list of adopters

Github user wendigo closed the pull request at: https://github.com/apache/mesos/pull/43 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request: Powered by - added Allegro Group.

Github user vi4m closed the pull request at: https://github.com/apache/mesos/pull/40 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled

[GitHub] mesos pull request: Powered by - added Allegro Group.

Github user vi4m commented on the pull request: https://github.com/apache/mesos/pull/40#issuecomment-105791244 Same company, can close this pull request --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] mesos pull request:

Github user intoeleven commented on the pull request: https://github.com/apache/mesos/commit/fe09d7de7f84de82f447d4321fe89912c06e402c#commitcomment-11352979 I can launch the cluster by default us-east-1b , but I changed default as eu-west-1a in mesos_ec2.py, it still can't launch and

[GitHub] mesos pull request:

Github user intoeleven commented on the pull request: https://github.com/apache/mesos/commit/fe09d7de7f84de82f447d4321fe89912c06e402c#commitcomment-11352747 Hi, I tried to install the latest mesos(0.22.1) on AWS by the steps from mesos documentation

[GitHub] mesos pull request: Powered by - added Allegro Group.

Github user davelester commented on the pull request: https://github.com/apache/mesos/pull/40#issuecomment-105639071 Thanks for this contribution, I just added Allegro to the Powered By Mesos list by applying this pull request: https://github.com/apache/mesos/pull/43 Is it

[GitHub] mesos pull request: Add Allegro to the list of adopters

Github user davelester commented on the pull request: https://github.com/apache/mesos/pull/43#issuecomment-105638062 Thanks for this contribution, I just pushed this to master. Could you please close this PR? --- If your project is set up for it, you can reply to this email and have

[GitHub] mesos pull request:

Github user intoeleven commented on the pull request: https://github.com/apache/mesos/commit/9d54ad4ee039af12dec05c4ef390645fc38479e7#commitcomment-11352719 Hi, I tried to install the latest mesos(0.22.1) on AWS by the steps from mesos documentation

[GitHub] mesos pull request: Add Allegro to the list of adopters

GitHub user wendigo opened a pull request: https://github.com/apache/mesos/pull/43 Add Allegro to the list of adopters We're using marathon on top of the mesos 0.22.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/wendigo/mesos

[GitHub] mesos pull request: Fix compiler error when building python module

GitHub user GregBowyer opened a pull request: https://github.com/apache/mesos/pull/42 Fix compiler error when building python module Mesos code uses c++11 which if the compiler does not specify its std leads to: ``` error: ‘function’ in namespace ‘std’ does

[GitHub] mesos pull request: Proposing addition of missing hashCode functio...

Github user pharshal commented on the pull request: https://github.com/apache/mesos/pull/39#issuecomment-90903233 Travis failure is unrelated. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have

[GitHub] mesos pull request: Update mesos-architecture.md

GitHub user emret opened a pull request: https://github.com/apache/mesos/pull/35 Update mesos-architecture.md Fix escaped chars You can merge this pull request into a Git repository by running: $ git pull https://github.com/emret/mesos patch-1 Alternatively you can review and

[GitHub] mesos pull request: Added Daemon

GitHub user farukd opened a pull request: https://github.com/apache/mesos/pull/29 Added Daemon You can merge this pull request into a Git repository by running: $ git pull https://github.com/farukd/mesos patch-1 Alternatively you can review and apply these changes as the

[GitHub] mesos pull request: Update mpiexec-mesos.in

GitHub user strat0sphere opened a pull request: https://github.com/apache/mesos/pull/28 Update mpiexec-mesos.in In the if statement [[ is used - [[ is a bash builtin command and is not available in sh. It will give an error ( [[: not found ) unless /bin/sh is a symbolic link to

[GitHub] mesos pull request: Added option to enable privileged mode for Doc...

Github user tnachen commented on the pull request: https://github.com/apache/mesos/pull/26#issuecomment-58766111 Are you running the unit test as is? The best way is to enable verbose logging and run the test again. Btw can you post your patch on reviewboard? Let's move it there

[GitHub] mesos pull request: Added option to enable privileged mode for Doc...

Github user minid33 commented on the pull request: https://github.com/apache/mesos/pull/26#issuecomment-58530671 @kmatzen Looks like this is the way your code enters an Apache project, I'd love for this change to go in, I need it a lot. --- If your project is set up for it, you can

[GitHub] mesos pull request: Added Vagrant and Ansible repo to the tools li...

GitHub user bspaans opened a pull request: https://github.com/apache/mesos/pull/25 Added Vagrant and Ansible repo to the tools list You can merge this pull request into a Git repository by running: $ git pull https://github.com/bspaans/mesos master Alternatively you can

[GitHub] mesos pull request: Fix for MESOS-1688

GitHub user MartinWeindel opened a pull request: https://github.com/apache/mesos/pull/24 Fix for MESOS-1688 As already explained in [MESOS-1688](https://issues.apache.org/jira/browse/MESOS-1688), there are schedulers allocating memory only for the executor and not for tasks. For

[GitHub] mesos pull request: Fix for MESOS-1688

Github user tnachen commented on the pull request: https://github.com/apache/mesos/pull/24#issuecomment-53287289 hi @MartinWeindel, can you post on reviewboard instead? That's how all the mesos patches are reviewed. --- If your project is set up for it, you can reply to this email

[GitHub] mesos pull request: Fix for MESOS-1688

Github user MartinWeindel closed the pull request at: https://github.com/apache/mesos/pull/24 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] mesos pull request: Fix for MESOS-1688

Github user MartinWeindel commented on the pull request: https://github.com/apache/mesos/pull/24#issuecomment-53337852 post on reviewboard will follow --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

[GitHub] mesos pull request: Clean help flags

Github user bmahler commented on a diff in the pull request: https://github.com/apache/mesos/pull/23#discussion_r15443932 --- Diff: src/master/flags.hpp --- @@ -61,7 +61,8 @@ class Flags : public logging::Flags add(Flags::work_dir, work_dir, -

[GitHub] mesos pull request: Add Sailthru to the Powered by Mesos page

Github user davelester commented on the pull request: https://github.com/apache/mesos/pull/21#issuecomment-48945644 Thanks! I just committed this, but it looks like asfbot didn't close this when I committed your patch. Could you close this request? --- If your project is set up for

[GitHub] mesos pull request: Add Sailthru to the Powered by Mesos page

Github user adgaudio closed the pull request at: https://github.com/apache/mesos/pull/21 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request: Deb packaging

Github user Sirupsen closed the pull request at: https://github.com/apache/mesos/pull/17 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request: Deb packaging

GitHub user Sirupsen opened a pull request: https://github.com/apache/mesos/pull/17 Deb packaging This adds https://github.com/mesosphere/mesos-deb-packaging into Mesos so we can build it with our current Debian package build process [described on the

[GitHub] mesos pull request: #MESOS-1209 bug fix for debian

GitHub user h4ck3rm1k3 opened a pull request: https://github.com/apache/mesos/pull/14 #MESOS-1209 bug fix for debian simple patch You can merge this pull request into a Git repository by running: $ git pull https://github.com/h4ck3rm1k3/mesos master Alternatively you can

[GitHub] mesos pull request: Update mesos-frameworks.md

GitHub user grandlogic opened a pull request: https://github.com/apache/mesos/pull/13 Update mesos-frameworks.md Added JobServer to the list of job schedulers that are implemented as Mesos Framework. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] mesos pull request: Update mesos-frameworks.md

Github user grandlogic commented on the pull request: https://github.com/apache/mesos/pull/13#issuecomment-39927070 Added JobServer to list of batch scheduler implemented as Mesos Framework. --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] mesos pull request: Update mesos-frameworks.md

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/13 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

<    1   2   3   4   5   6