From: Ricardo Wurmus <rekado@elephly.net>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Sharlatan Hellseher <sharlatanus@gmail.com>,
guix-devel@gnu.org, ngraves@ngraves.fr, jgart@dismail.de,
felgru@posteo.net
Subject: Re: Status of python-team branch
Date: Mon, 02 Sep 2024 18:00:38 +0200 [thread overview]
Message-ID: <87h6ayhwpl.fsf@elephly.net> (raw)
In-Reply-To: <87ttfpcytn.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 12 Aug 2024 21:42:44 +0200")
Ricardo Wurmus <rekado@elephly.net> writes:
> Lars-Dominik Braun <lars@6xq.net> writes:
>
>> Hi,
>>
>>> I'd like to check who is working on python-team branch to prepare it for
>>> the merge?
>>
>> I don’t think anyone is actively working on it right now. #71408 is
>> the place where any updates should be if there were any. CC’ing a few
>> people who have contributed to the branch or stated they have interest,
>> just to be sure.
>
> I'm currently on leave, but I think it would make sense to rebase
> python-team on top of core-updates.
>
> My last contributions were to core-updates, not to python-team. Since
> core-updates is next in line to be merged I think our next step should
> be to rebase python-team before any more incompatible work is done on
> that branch.
Now that core-updates has been merged, the python-team branch would be
next in line for a merge.
Is anyone interested in rebasing the branch?
--
Ricardo
next prev parent reply other threads:[~2024-09-02 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 10:27 Status of python-team branch Sharlatan Hellseher
2024-08-12 16:24 ` Lars-Dominik Braun
2024-08-12 19:42 ` Ricardo Wurmus
2024-09-02 16:00 ` Ricardo Wurmus [this message]
2024-09-02 17:45 ` Sharlatan Hellseher
2024-09-02 20:16 ` jgart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6ayhwpl.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=felgru@posteo.net \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=ngraves@ngraves.fr \
--cc=sharlatanus@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).