On 2016-10-23 14:48 , Jeremy Huddleston Sequoia wrote:
On Oct 21, 2016, at 18:16, Clemens Lang wrote:
Hello MacPorts users and developers,
On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
Due to the current SVN and Trac downtime, we are also discussing to
make the move of Trac
> On Oct 22, 2016, at 22:48, Jeremy Huddleston Sequoia
> wrote:
>
>
>> On Oct 21, 2016, at 18:16, Clemens Lang wrote:
>>
>> Hello MacPorts users and developers,
>>
>>> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
>>> Due to the current SVN and Trac downtime, we are also di
> On Oct 21, 2016, at 18:16, Clemens Lang wrote:
>
> Hello MacPorts users and developers,
>
> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
>> Due to the current SVN and Trac downtime, we are also discussing to
>> make the move of Trac sooner if that helps us restore service ear
On Sun, Oct 23, 2016 at 1:44 AM, Ryan Schmidt
wrote:
> a change Apple made to their network configuration which had unexpected
> consequences
Maybe it is not related but I have suffered serious synchronization issues
in iCloud services.
--
Eneko Gotzon Ares
enekogot...@gmail.com
___
> On Oct 22, 2016, at 16:11, Fielding, Eric J (329A)
> wrote:
>
> I am guessing that the lack of access to MacPorts yesterday (Friday) may have
> been related to the massive DDoS attack on the Dyn DNS servers. Because Dyn
> uses their content delivery network to provide DNS, different areas we
> On Oct 22, 2016, at 5:11 PM, Fielding, Eric J (329A)
> wrote:
>
> I am guessing that the lack of access to MacPorts yesterday (Friday)
> may have been related to the massive DDoS attack on the Dyn DNS
> servers.
This seems unlikely to me, as our unplanned downtime began (I think) on
Thursday
I am guessing that the lack of access to MacPorts yesterday (Friday) may have
been related to the massive DDoS attack on the Dyn DNS servers. Because Dyn
uses their content delivery network to provide DNS, different areas were
affected to differing degrees from what I saw reported. The regular M
> On Oct 22, 2016, at 9:40 AM, Marko Käning wrote:
>
>> On 22 Oct 2016, at 15:34 , Ryan Schmidt wrote:
>>
>> as well as the "hub" command line program in the "hub" port.
>
> Exactly, that’s the one I meant. Perhaps it’s worth mentioning it on the
> wiki page.
I've added several tools to the l
On 22 Oct 2016, at 15:34 , Ryan Schmidt wrote:
> There's the "git" command line program in the "git" port,
:-) Hahaha. Yes, of course! ;-)
> as well as the "hub" command line program in the "hub" port.
Exactly, that’s the one I meant. Perhaps it’s worth mentioning it on the
wiki page. Haven’t
> On Oct 22, 2016, at 7:49 AM, Marko Käning wrote:
>
> Hi Clemens,
>
> On 22 Oct 2016, at 14:41 , Clemens Lang wrote:
>> Developers will merge them, either using the command line client, or the
>> GitHub UI. We haven't decided and documented which merge method to use,
>> although I'd prefer th
On 22 Oct 2016, at 14:49 , Joshua Root wrote:
> Please see the Migration Timeline section in the first message in this
> thread. Developers cannot yet push to the git repos.
yes, I figured that now.
OK, awaiting you guys’ decisions on the new workflow.
___
Hi Clemens,
On 22 Oct 2016, at 14:41 , Clemens Lang wrote:
> Developers will merge them, either using the command line client, or the
> GitHub UI. We haven't decided and documented which merge method to use,
> although I'd prefer the rebase.
ok, I see.
BTW, you’ve mentioned in some thread latel
On 2016-10-22 23:31 , Marko Käning wrote:
Hi Clemens,
great to see the GitHub conversion progressing this rapidly! Thumbs up from
me!!!
When reading the WorkingWithGit wiki page [1] I saw how port contributors can
post
their suggestions to MacPorts via "Pull Requests”, yet it does not get cl
Hi,
On Sat, Oct 22, 2016 at 02:31:32PM +0200, Marko Käning wrote:
> When reading the WorkingWithGit wiki page [1] I saw how port
> contributors can post their suggestions to MacPorts via "Pull
> Requests”, yet it does not get clear from that text how those PRs will
> then actually be included into
Hi Clemens,
great to see the GitHub conversion progressing this rapidly! Thumbs up from
me!!!
When reading the WorkingWithGit wiki page [1] I saw how port contributors can
post
their suggestions to MacPorts via "Pull Requests”, yet it does not get clear
from
that text how those PRs will then
Hi,
On Sat, Oct 22, 2016 at 07:54:20AM -0400, Richard Cobbe wrote:
> Is there/will there be a story for people who cannot use rsync to pull
> down updates because they're behind a restrictive proxy?
>
> This affects one of the three computers on which I maintain a MacPorts
> installation. I curr
> On Oct 22, 2016, at 6:54 AM, Richard Cobbe wrote:
>
> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
>> Hello MacPorts users and developers,
>>
>> MacPorts will be moving to GitHub soon. We're sending this email to
>> inform you about changes in how you access the MacPorts repo
> On 22 Oct 2016, at 12:54 pm, Richard Cobbe wrote:
>
>> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
>> Hello MacPorts users and developers,
>>
>> MacPorts will be moving to GitHub soon. We're sending this email to
>> inform you about changes in how you access the MacPorts re
On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
> Hello MacPorts users and developers,
>
> MacPorts will be moving to GitHub soon. We're sending this email to
> inform you about changes in how you access the MacPorts repositories and
> bug tracker. Additionally, this email contains in
19 matches
Mail list logo
