On 23 May 2018 at 19:25, Paul Moore wrote:
> On 23 May 2018 at 09:14, Antoine Pitrou wrote:
> > On Tue, 22 May 2018 19:10:49 -0500
> > Tim Peters wrote:
> >
> >> Thanks for that! It instantly cleared up several mysteries for me.
On 23 May 2018 at 09:14, Antoine Pitrou wrote:
> On Tue, 22 May 2018 19:10:49 -0500
> Tim Peters wrote:
>
>> Thanks for that! It instantly cleared up several mysteries for me.
>> I'm just starting to learn git & github, and am starkly reminded of an
>>
Tim Peters writes:
> there is absolutely nothing "obvious" about source-control systems,
> or workflows, before you already know them ;-)
Obvious, adj.: More an expletive than a true adjective, shows a state
of mind in which the speaker is comfortable that a statement fits her
preconceptions.
On Tue, 22 May 2018 19:10:49 -0500
Tim Peters wrote:
> [Nathaniel Smith ]
> > ...
> > As far as git is concerned, the main repo on github, your fork on
> > github, and your local repo are 3 independent repositories, equally
> > valid. The relationships
[Nathaniel Smith ]
> ...
> As far as git is concerned, the main repo on github, your fork on
> github, and your local repo are 3 independent repositories, equally
> valid. The relationships between them are purely a matter of
> convention.
Thanks for that! It instantly cleared up
On Tue, May 22, 2018 at 3:51 PM, Skip Montanaro
wrote:
>> You don't really need copies of official branches on your Github fork if
> you're not a maintainer for these branches.
>
> I explicitly wanted to run with 3.7 in the run-up to release. On that
> branch, the built
On May 22, 2018, at 18:51, Skip Montanaro wrote:
> [Ivan Pozdeev]:
>> You don't really need copies of official branches on your Github fork
>> if you're not a maintainer for these branches.
> I explicitly wanted to run with 3.7 in the run-up to release. On that
> branch,
> You don't really need copies of official branches on your Github fork if
you're not a maintainer for these branches.
I explicitly wanted to run with 3.7 in the run-up to release. On that
branch, the built ./python reports 3.7.0b4+ at startup. Master tells me
3.8.0a0 on startup. Since my local
On 22.05.2018 3:07, Skip Montanaro wrote:
My GitHub fork of the cpython repo was made awhile ago, before a 3.7 branch
was created. I have no remotes/origin/3.7. Is there some way to create it
from remotes/upstream/3.7? I asked on GitHub's help forums. The only
recommendation was to to delete my
On Tue, May 22, 2018 at 10:45 AM, Skip Montanaro
wrote:
>> Create it from upstream? Yep! Try this:
>
>> git checkout -b 3.7 upstream/3.7
>> git push -u origin 3.7
>
> Thanks, Chris! Didn't have to chug for too long either, just a few seconds.
>
> S
Perfect! I'm used to
> Create it from upstream? Yep! Try this:
> git checkout -b 3.7 upstream/3.7
> git push -u origin 3.7
Thanks, Chris! Didn't have to chug for too long either, just a few seconds.
S
___
Python-Dev mailing list
Python-Dev@python.org
On Tue, May 22, 2018 at 10:07 AM, Skip Montanaro
wrote:
> My GitHub fork of the cpython repo was made awhile ago, before a 3.7 branch
> was created. I have no remotes/origin/3.7. Is there some way to create it
> from remotes/upstream/3.7? I asked on GitHub's help forums.
My GitHub fork of the cpython repo was made awhile ago, before a 3.7 branch
was created. I have no remotes/origin/3.7. Is there some way to create it
from remotes/upstream/3.7? I asked on GitHub's help forums. The only
recommendation was to to delete my fork and recreate it. That seemed kind
of
13 matches
Mail list logo