On 4 November 2016 at 18:55, Marko Käning wrote:
>
> Besides there is even a clearly visible RED "Work-In-Progress" label
> available in the PR interface, which Mojca had spotted eventually.
I didn't spot it. I though it was useful and made it after this
discussion was started.
Mojca
___
On 04 Nov 2016, at 02:19 , Arno Hautala wrote:
> But, it occurs to me that one of the goals of moving
> to GitHub is greater collaboration and that is facilitated by inline
> comments on the pull request. Plus, a completed pull request is one
> comment away from a work in progress anyway.
+1
>
Hi Rainer,
On 03 Nov 2016, at 18:57 , Sterling Smith wrote:
> On Nov 3, 2016, at 10:47AM, Rainer Müller wrote:
>
>> On 2016-11-03 17:49, Sterling Smith wrote:
>>> The main question of procedure is: Should the main macports repo be
>>> used for proposing review of work in progress via pull reque
>>> The main question of procedure is: Should the main macports repo be
>>> used for proposing review of work in progress via pull requests? If
>>> not, what is the proposed method?
>>
>> I propose you put your changes on a branch, add the compare URL to a
>> ticket or send an email to macports-de
On Nov 3, 2016, at 10:47AM, Rainer Müller wrote:
> On 2016-11-03 17:49, Sterling Smith wrote:
>> The main question of procedure is: Should the main macports repo be
>> used for proposing review of work in progress via pull requests? If
>> not, what is the proposed method?
>
> I propose you put
On 2016-11-03 17:49, Sterling Smith wrote:
> The main question of procedure is: Should the main macports repo be
> used for proposing review of work in progress via pull requests? If
> not, what is the proposed method?
I propose you put your changes on a branch, add the compare URL to a
ticket o
