unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "jgart" <jgart@dismail.de>
To: "Sharlatan Hellseher" <sharlatanus@gmail.com>,
	"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>,
	"Felix Gruber" <felgru@posteo.net>,
	"Steve George" <steve@futurile.net>
Subject: Re: Status of python-team branch
Date: Thu, 26 Sep 2024 17:27:57 +0000	[thread overview]
Message-ID: <009929435a373a0b7600f6a0304bdadb8097b5bb@dismail.de> (raw)
In-Reply-To: <CAO+9K5qdQA3Lynj84j3VhDJxJB+_spBi-zU5+xJAHE4aBfG9Bw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 515 bytes --]

> 
> Same for me, starting resolving rebase conflict.
> 
Hi Guixers,

I would recommend cherry picking logical commits into new branches that can be quickly reviewed and merged by Guix volunteers.

Steve made a list here of some logical commits that can go into new branches:

https://issues.guix.gnu.org/71408#11

Feel free to send small patch sets of those for review by Guix volunteers to look at.

I can take some time to review and apply such small patches and test them.

all the best,

jgart

[-- Attachment #2: Type: text/html, Size: 1027 bytes --]

  reply	other threads:[~2024-09-26 19:04 UTC|newest]

Thread overview: 12+ 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
2024-09-26 17:27             ` jgart [this message]
2024-09-26 22:15               ` Steve George
  -- strict thread matches above, loose matches on Subject: below --
2024-09-24 11:03 Sharlatan Hellseher
2024-09-24 13:28 ` Arseniy Zaostrovnykh

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=009929435a373a0b7600f6a0304bdadb8097b5bb@dismail.de \
    --to=jgart@dismail.de \
    --cc=felgru@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=lars@6xq.net \
    --cc=mail@cbaines.net \
    --cc=ngraves@ngraves.fr \
    --cc=rekado@elephly.net \
    --cc=sharlatanus@gmail.com \
    --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).