On 10/29/16 7:19 AM, Clemens Lang wrote:
> On Fri, Oct 28, 2016 at 07:58:16AM -0700, David Evans wrote:
>> Considering that this is a significant event, I'd appreciate it (and
>> others might as well) if a specific date & time, expressed in UTC,
>> could be published today for the disabling of subv
On Fri, Oct 28, 2016 at 07:58:16AM -0700, David Evans wrote:
> Considering that this is a significant event, I'd appreciate it (and
> others might as well) if a specific date & time, expressed in UTC,
> could be published today for the disabling of subversion write access.
We'll try to keep write
On 10/28/16 7:18 AM, Rainer Müller wrote:
> On 2016-10-28 16:02, Craig Treleaven wrote:
>>> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
>>> ...
>>> Migration Timeline
>>> ==
>>> The switch to Git will happen on the weekend of October 29th/30th. ...
>>
>> Is this still on track
On 2016-10-28 16:02, Craig Treleaven wrote:
>> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
>> ...
>> Migration Timeline
>> ==
>> The switch to Git will happen on the weekend of October 29th/30th. ...
>
> Is this still on track?
Yes, expect Subversion to go read-only this wee
> On Oct 28, 2016, at 9:02 AM, Craig Treleaven wrote:
>
>> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
>> ...
>> Migration Timeline
>> ==
>> The switch to Git will happen on the weekend of October 29th/30th. ...
>
> Is this still on track?
Yes.
_
> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
> ...
> Migration Timeline
> ==
> The switch to Git will happen on the weekend of October 29th/30th. ...
Is this still on track?
Craig
___
macports-users mailing list
macports-users@lis
> 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
On 2016-10-21, at 8:03 PM, Lawrence Velázquez wrote:
>> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote:
>>
>>> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote:
>>>
On Oct 21, 2016, at 10:20 PM, Craig Treleaven
wrote:
Also, is the consensus that a graphical user
On 2016-10-21, at 8:03 PM, Lawrence Velázquez wrote:
>> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote:
>>
>>> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote:
>>>
On Oct 21, 2016, at 10:20 PM, Craig Treleaven
wrote:
Also, is the consensus that a graphical user
> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote:
>
>> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote:
>>
>>> On Oct 21, 2016, at 10:20 PM, Craig Treleaven
>>> wrote:
>>>
>>> Also, is the consensus that a graphical user interface over git
>>> more likely to be harmful than helpful?
> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote:
>
>> On Oct 21, 2016, at 10:20 PM, Craig Treleaven
>> wrote:
>>
>> However, would it be possible to add a tangible example of updating
>> a port to that page?
>>
>> I know a little bit about Subversion and less about Git. I would li
> On Oct 21, 2016, at 10:20 PM, Craig Treleaven wrote:
>
> However, would it be possible to add a tangible example of updating
> a port to that page?
>
> I know a little bit about Subversion and less about Git. I would like
> to see a soup-to-nuts example of cloning the ports tree, updating
>
> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
>
> Hello MacPorts users and developers,
>
> ... Please read through
> https://trac.macports.org/wiki/WorkingWithGit
> which contains a number of guidelines for working with the MacPorts Git
> repositories.
>
The Working with Git page is pretty
Thank you Clemens. That is great.
Cheers,
Joe
On Fri, Oct 21, 2016 at 11:12 AM, 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 tr
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 information on planned
downtimes.
Action Required: GitHub Accounts
26 matches
Mail list logo
