From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: Ricardo Wurmus <rekado@elephly.net>,
Lars-Dominik Braun <lars@6xq.net>,
guix-devel <guix-devel@gnu.org>,
Nicolas Graves <ngraves@ngraves.fr>, jgart <jgart@dismail.de>,
Felix Gruber <felgru@posteo.net>
Subject: Re: Status of python-team branch
Date: Thu, 26 Sep 2024 17:14:33 +0100 [thread overview]
Message-ID: <CAO+9K5qdQA3Lynj84j3VhDJxJB+_spBi-zU5+xJAHE4aBfG9Bw@mail.gmail.com> (raw)
In-Reply-To: <87wmiy5uir.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Hi,
Same for me, starting resolving rebase conflict.
I'm finishing go-team right now and will have some free time on Sat.
Thanks,
Oleg
On Thu, 26 Sept 2024, 16:01 Christopher Baines, <mail@cbaines.net> wrote:
> Sharlatan Hellseher <sharlatanus@gmail.com> writes:
>
> > Hi,
> >
> > I may volunteer myself to that
> > - rebase on current master
> > - resolve conflicts
> > - apply pending patches from issues
> > - push for testing
> > - merge to master
> >
> > Is anyone interested in rebasing the branch?
>
> Are you still looking at rebasing python-team?
>
> I've looked at it myself, but I've got stuck with the big "gnu: Add
> python-setuptools/python-wheel where necessary."
> (Icd7699fc1dc56e974ae7568f2ae916dbf876bea5) commit.
>
[-- Attachment #2: Type: text/html, Size: 1393 bytes --]
next prev parent reply other threads:[~2024-09-26 16:17 UTC|newest]
Thread overview: 15+ 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
2024-09-02 17:45 ` Sharlatan Hellseher
2024-09-02 20:16 ` jgart
2024-09-26 15:01 ` Christopher Baines
2024-09-26 16:14 ` Sharlatan Hellseher [this message]
2024-09-26 17:27 ` jgart
2024-09-26 22:15 ` Steve George
2024-10-17 10:27 ` Sharlatan Hellseher
-- strict thread matches above, loose matches on Subject: below --
2024-09-24 11:03 Sharlatan Hellseher
2024-09-24 13:28 ` Arseniy Zaostrovnykh
2024-11-05 13:47 Sharlatan Hellseher
2024-11-05 15:11 ` Tanguy LE CARROUR
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=CAO+9K5qdQA3Lynj84j3VhDJxJB+_spBi-zU5+xJAHE4aBfG9Bw@mail.gmail.com \
--to=sharlatanus@gmail.com \
--cc=felgru@posteo.net \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=mail@cbaines.net \
--cc=ngraves@ngraves.fr \
--cc=rekado@elephly.net \
/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).