So, I should add a Python teams specific section to the texinfo docs?
Hi jgart,
"jgart" writes:
> Thanks, I ended up doing what you suggested.
>
> Should we document this git branch policy for contributors with commit access
> in the manual?
>
> I think we should state it explicitly so there is no confusion for new
> contributors with commit access.
If document
Thanks, I ended up doing what you suggested.
Should we document this git branch policy for contributors with commit access
in the manual?
I think we should state it explicitly so there is no confusion for new
contributors with commit access.
all best,
jgart
Hi,
Lars-Dominik Braun writes:
> Hi,
>
>> What is the git approach for keeping the Python branch up to date? 🦆
>> Should I be rebasing off of master or something else?
>
> yeah, that’s generally what I would do before working on it. Note that
> you cannot force-push into Savannah. You have to re
Hi,
> What is the git approach for keeping the Python branch up to date? 🦆
> Should I be rebasing off of master or something else?
yeah, that’s generally what I would do before working on it. Note that
you cannot force-push into Savannah. You have to remove the remote branch
and create it again.
Hi Lars,
What is the git approach for keeping the Python branch up to date? 🦆
Should I be rebasing off of master or something else?
I'm trying to review this patch:
https://issues.guix.gnu.org/64973
Any advice much appreciated.
all best,
jgart
