> On Aug 20, 2016, at 11:55 PM, Brandon Allbery wrote:
>
>> On Sat, Aug 20, 2016 at 11:44 PM, Ian Wadham wrote:
>> Fork the repo??
>
> github expects you to do this, yes. I don't actually recommend it because
> keeping up to date with the original repo's a PITA (and *not* automated in
> any w
On Sat, Aug 20, 2016 at 11:44 PM, Ian Wadham wrote:
> Fork the repo??
github expects you to do this, yes. I don't actually recommend it because
keeping up to date with the original repo's a PITA (and *not* automated in
any way. https://help.github.com/articles/syncing-a-fork/ is annoyingly
manu
On 20/08/2016, at 11:51 PM, Ryan Schmidt wrote:
>
> On Aug 19, 2016, at 10:24 PM, Lawrence Velázquez wrote:
>
>> Any documentation we write should be written specifically for developers
>>
>> 1. who are accustomed to using Subversion, and
>> 2. want to translate *their MacPorts workfl
On 20/08/2016, at 1:24 PM, Lawrence Velázquez wrote:
>> On Aug 19, 2016, at 11:16 PM, Ian Wadham wrote:
>> As a KDE developer (and spectator of the changeover from svn to git) I have
>> found
>> this cheat sheet very useful, but not quite covering all situations I have
>> encountered.
>> htt
Hi Lawrence,
On 20 Aug 2016, at 19:48 , Lawrence Velázquez wrote:
> How can you play the n00b if you're so fluent? :P
I can tell you: I CAN! :-)
Have proven this umpteen times.
Many of my coworkers tell me that I am the ideal tester! No joking.
8-D
Greets,
Marko
_
> On Aug 20, 2016, at 1:39 PM, Marko Käning wrote:
>
> I’d happily clone the official MacPorts git repo (also before it is live) and
> try to create pull-requests and play the newbee there, because I think that’s
> the best way to ensure foolproofness for the new system.
>
> I am quite fluent
Hi Clemens,
if you need an independent tester for your MacPorts workflows on GitHub
I am herewith offering my support.
I’d happily clone the official MacPorts git repo (also before it is live)
and try to create pull-requests and play the newbee there, because I think
that’s the best way to ensure
Dear Ryan,
On 20 Aug 2016, at 02:18 , Ryan Schmidt wrote:
> I'm pleased to announce that MacPorts will be moving its source code to
> GitHub.
in general I applaud this move! Congratulations to all those involved to make
this change happen!!!
> great collaboration features such as pull requests
I'm familiar with tig and gitk, if anyone needs assistance with those.
On 08/19/2016 09:49 PM, Mark Anderson wrote:
> I use git (and Github Enterprise) in my day to day work. I can help out.
>
> Another good (free (as in beer)) client is SourceTree
> https://www.sourcetreeapp.com/
___
On Aug 19, 2016, at 10:24 PM, Lawrence Velázquez wrote:
> Any documentation we write should be written specifically for developers
>
> 1. who are accustomed to using Subversion, and
> 2. want to translate *their MacPorts workflow* to Git.
>
> We shouldn't expend effort rewriting a s
> On Aug 20, 2016, at 12:47 AM, Ian Wadham wrote:
>
> Hi Lawrence,
>
> On 20/08/2016, at 1:24 PM, Lawrence Velázquez wrote:
>>> On Aug 19, 2016, at 11:16 PM, Ian Wadham wrote:
>>>
>>> Qt and KDE moved from svn to git a while back. IIRC it was quite an effort
>>> for a
>>> few individuals to
> On Aug 19, 2016, at 9:37 AM, m...@macports.org wrote:
>
> Revision
> 151665
> Author
> m...@macports.org
> Date
> 2016-08-19 07:37:38 -0700 (Fri, 19 Aug 2016)
> Log Message
>
> snort: Add missing rules files from default snort.conf. (#46320)
> Modified Paths
>
> • trunk/dports/net/snort
On 2016-8-20 11:04 , Kevin Walzer wrote:
On 8/19/16 8:18 PM, Ryan Schmidt wrote:
Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the
decade since Mac OS Forge was created, collaborative software development
platforms like GitHub and BitBucket have become very popular and
su
13 matches
Mail list logo
