From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: guix-devel@gnu.org
Cc: Lars-Dominik Braun <lars@6xq.net>,
Ricardo Wurmus <rekado@elephly.net>,
Steve George <steve@futurile.net>,
Christopher Baines <mail@cbaines.net>, jgart <jgart@dismail.de>,
Arseniy Zaostrovnykh <necto.ne@gmail.com>
Subject: Status of python-team branch
Date: Thu, 17 Oct 2024 11:27:02 +0100 [thread overview]
Message-ID: <878qx211ec.fsf@gmail.com> (raw)
Message-ID: <20241017102702.BY0H7rq8Kq8HrkIrQmFVDH9UlihGyisfhPkvuU7z4O4@z> (raw)
In-Reply-To: 878qx211ec.fsf@gmail.com
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
Hi python-team@guix!
I finally found some time to complete rebasing process of python-team on
master, few commits were not required.
New rebased python-team branch is pushed for CI to pick it up.
Older branch is renamed to python-team-old for future reference before
merging python-team to master.
As far as I could noticed during rebase task the main changes is
refreshed pyproject-build-system and Python packages migration to it.
There are a few branches in a queue to be merged, let's see how many
adjustments python-team needs to be applied before placing it on the
queue.
Rebased on d95588242c605fbb72e25fe36a0903a1538e9018 from master.
Thanks,
Oleg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2024-10-17 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 10:27 Sharlatan Hellseher [this message]
2024-08-12 16:24 ` Status of python-team branch 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
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=878qx211ec.fsf@gmail.com \
--to=sharlatanus@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=mail@cbaines.net \
--cc=necto.ne@gmail.com \
--cc=rekado@elephly.net \
--cc=steve@futurile.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).