> On Nov 10, 2016, at 9:57 AM, Ryan Schmidt wrote:
>
>> On Nov 10, 2016, at 8:55 AM, Rainer Müller wrote:
>>
>> "Resolves" is not a keyword recognized by the CommitTicketUpdater,
>> use "Closes", "Fix", or "Fixes".
>
> Can't remember what it supports.
>
> It should recognize "Resolves"; we've
On 10 November 2016 at 10:43, René J.V. Bertin wrote:
>
> How complicated would it be to set up the fork such that you can put custom
> ports in the default branch, and set up another branch to track the official
> ports tree? I have a hunch that it shouldn't be too hard to do in .git/config
> o
> On Nov 10, 2016, at 8:55 AM, Rainer Müller wrote:
>
> On 2016-11-10 15:19, Ryan Schmidt wrote:
>> Ryan Schmidt (ryandesign) pushed a commit to branch master
>> in repository macports-ports.
>>
>>
>> https://github.com/macports/macports-ports/commit/4e836559279a752ee090ed4aa8f1b0c3aa7d0a9a
>>
On 2016-11-10 15:19, Ryan Schmidt wrote:
> Ryan Schmidt (ryandesign) pushed a commit to branch master
> in repository macports-ports.
>
> https://github.com/macports/macports-ports/commit/4e836559279a752ee090ed4aa8f1b0c3aa7d0a9a
>
> commit 4e836559279a752ee090ed4aa8f1b0c3aa7d0a9a Author: Ryan Schmi
Thank you for the explanation. Indeed, my problem was that the Portindex was
out of date and not being updated, because the Portfiles had time stamps older
than the Portindex itself.
Cheers
Artur
From: Clemens Lang [c...@macports.org]
Sent: 09 November
Out of curiosity:
The typical situation for ports tree forks will be that the master branch
tracks macports-ports/origin/master while anything personal/custom will be kept
in a personal branch.
How complicated would it be to set up the fork such that you can put custom
ports in the default bra
