@tommy while I understand the frustration, one big problem I have with
doing reviews on GitHub is that the interface is really bad in terms of
capturing revision sets across patch submissions and capturing dependencies
across patches. Once a contributors updates an existing patch-set, all
comments
+1
On Tue, Jun 6, 2017 at 7:13 PM Mao Geng
wrote:
> Well said
> +1 to github
>
> > On Jun 6, 2017, at 6:59 PM, Klaus Ma wrote:
> >
> > +1
> >
> >> On 7 Jun 2017, at 09:56, tommy xiao wrote:
> >>
> >> Hi team,
> >>
> >> yesterday sometime, in a china local mesos developer group, a Tencent's
> >
Well said
+1 to github
> On Jun 6, 2017, at 6:59 PM, Klaus Ma wrote:
>
> +1
>
>> On 7 Jun 2017, at 09:56, tommy xiao wrote:
>>
>> Hi team,
>>
>> yesterday sometime, in a china local mesos developer group, a Tencent's
>> developer report a issue about docker executor fetcher can't correct set
+1
> On 7 Jun 2017, at 09:56, tommy xiao wrote:
>
> Hi team,
>
> yesterday sometime, in a china local mesos developer group, a Tencent's
> developer report a issue about docker executor fetcher can't correct set
> file's owner. with detail chat, we found this is bug. So we guide the
> developer
Hi team,
yesterday sometime, in a china local mesos developer group, a Tencent's
developer report a issue about docker executor fetcher can't correct set
file's owner. with detail chat, we found this is bug. So we guide the
developer howto contributor to mesos project. in the same time, we found
t
Github user rukletsov commented on the issue:
https://github.com/apache/mesos/pull/216
Could you please provide more context for this PR?
---
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 user shendabin opened a pull request:
https://github.com/apache/mesos/pull/216
1.3.x
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/mesos 1.3.x
Alternatively you can review and apply these changes as the patch at:
