Hi,
On Mon, Oct 31, 2016 at 10:25:33AM +0100, Davide Liessi wrote:
> I have just noticed in one of my GitHub repositories that in Settings
> -> Options there is a "Merge button" section that lets you
> enable/disable the behaviours of the merge button described in the
> above link.
> Maybe you cou
2016-10-25 15:35 GMT+02:00 Ryan Schmidt :
>
>> On Oct 25, 2016, at 6:54 AM, Rainer Müller wrote:
>>
>> On 2016-10-25 10:36, Ryan Schmidt wrote:
>>>
>>>
>>> On Oct 24, 2016, at 17:57, Clemens Lang wrote:
>>>
> On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote:
> A description of
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-dev mailing list
macports-dev@lists.m
> On Oct 25, 2016, at 6:54 AM, Rainer Müller wrote:
>
> On 2016-10-25 10:36, Ryan Schmidt wrote:
>>
>>
>> On Oct 24, 2016, at 17:57, Clemens Lang wrote:
>>
On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote:
A description of how exactly one would rebase (potentially squas
On 2016-10-25 10:36, Ryan Schmidt wrote:
>
>
> On Oct 24, 2016, at 17:57, Clemens Lang wrote:
>
>>> On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote:
>>> A description of how exactly one would rebase (potentially squash and
>>> history-rewrite) a submitted PR onto current master sho
On Oct 24, 2016, at 17:57, Clemens Lang wrote:
>> On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote:
>> A description of how exactly one would rebase (potentially squash and
>> history-rewrite) a submitted PR onto current master should be on our
>> WorkingWithGit wiki page.
>
> the
Hi,
On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote:
> A description of how exactly one would rebase (potentially squash and
> history-rewrite) a submitted PR onto current master should be on our
> WorkingWithGit wiki page.
the easiest approach is just clicking the button that does t
I fully agree with Mojca, that it is better to work on a private fork for the
start and let others - like Clemens suggested - take part in reviewing on that
forked repository. This way one can train what would have to be done on the
main macports-ports repo before causing trouble there...
On 2
On Mon, Oct 24, 2016 at 08:22:38PM +0200, Mojca Miklavec wrote:
> Even if the method of achieving this is not prescribed***, I wouldn't
> mind a bit of testing before screwing up the real repository.
>
> *** But having some cheatsheet would help.
Sure, feel free to create a fork, play around, add
>
> You should check with the developers of Coda on their Git support. I
> don't think a tool built especially for website editing will be the best
> choice, but maybe it works for you.
Otherwise I also use PyCharm free edition for some Python related tasks, and it
seems to have built-in GitHub
On 24 October 2016 at 20:08, Lawrence Velázquez wrote:
>> On Oct 24, 2016, at 1:58 PM, Clemens Lang wrote:
>>> On Mon, Oct 24, 2016 at 07:47:18PM +0200, Mojca Miklavec wrote:
>>>
>>> (My preference would be to keep linear history for master and not to
>>> keep ten broken revisions of a Portfile res
> On Oct 24, 2016, at 1:58 PM, Clemens Lang wrote:
>
> I don't think we should mandate a complex "run these magic git commands"
> workflow. Making things complicated will just make them go wrong.
Agreed.
>> On Mon, Oct 24, 2016 at 07:47:18PM +0200, Mojca Miklavec wrote:
>>
>> (My preference wo
Hi,
On Mon, Oct 24, 2016 at 08:00:04PM +0200, Vincent Habchi wrote:
> I’ve bought Coda 2 when I use to do a bit of HTML development. Can I
> use it to check out - tinker with the new MacPorts GIT repository?
You should check with the developers of Coda on their Git support. I
don't think a tool b
> On Oct 24, 2016, at 2:00 PM, Vincent Habchi wrote:
>
> I’ve bought Coda 2 when I use to do a bit of HTML development. Can
> I use it to check out - tinker with the new MacPorts GIT repository?
You can use any Git client you like, as long as you're aware that we'll
effectively be trashing the c
Guys,
I’ve bought Coda 2 when I use to do a bit of HTML development. Can I use it to
check out - tinker with the new MacPorts GIT repository?
TIA,
Vincent
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mai
On Mon, Oct 24, 2016 at 07:47:18PM +0200, Mojca Miklavec wrote:
> I can send you a screenshot comparing the version I opened two hours
> ago and the same page reloaded just now. The result changed in the
> meantime. In any case I can no longer provide you any broken example
> (there are still some
On 24 October 2016 at 19:15, Lawrence Velázquez wrote:
>> On Oct 24, 2016, at 12:50 PM, Mojca Miklavec wrote:
>>
>> (not?) related to the above question: One thing I'm confused about is
>> that whenever I'm listed as a reporter or in CC, my name would be
>> replaced by all the three data (my macpor
> On Oct 24, 2016, at 12:15, Lawrence Velázquez wrote:
>
> The "macports-ports" repository
> (https://github.com/macports/macports-ports.git) already contains
> a stale version of the ports tree; you can fork it and play around with
> it as you wish.
If you clone or fork any of the preliminary
Hi,
On Mon, Oct 24, 2016 at 06:50:47PM +0200, Mojca Miklavec wrote:
> Is that true also for any other email we used prior to becoming
> committers?
Yes.
> Can new emails be added later?
Yes, but you'll have to relogin.
> How exactly does it work when people enter multiple emails? (Judging
> fr
> On Oct 24, 2016, at 12:50 PM, Mojca Miklavec wrote:
>
>> On 21 October 2016 at 20:12, Clemens Lang wrote:
>>
>> Action Required: GitHub Accounts
>>
>> Our new Trac installation will use GitHub for login. If you do not have
>> a GitHub account yet, please create
Hi,
On 21 October 2016 at 20:12, Clemens Lang wrote:
>
> Action Required: GitHub Accounts
>
> Our new Trac installation will use GitHub for login. If you do not have
> a GitHub account yet, please create one now at
> https://github.com/join
>
> To help us match yo
> 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
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
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
37 matches
Mail list logo
