unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars-Dominik Braun <lars@6xq.net>
To: jgart <jgart@dismail.de>
Cc: "Sharlatan Hellseher" <sharlatanus@gmail.com>,
	me@bonfacemunyoki.com, "Ludovic Courtès" <ludo@gnu.org>,
	"Christopher Baines" <mail@cbaines.net>,
	marius@gnu.org, 71408@debbugs.gnu.org, tanguy@bioneland.org,
	"Nicolas Graves" <ngraves@ngraves.fr>
Subject: [bug#71408] Request for merging "python-team" branch
Date: Sun, 30 Jun 2024 09:31:36 +0200	[thread overview]
Message-ID: <ZoEJ2Fhf-XLeGSsu@noor.fritz.box> (raw)
In-Reply-To: <e2bd1188f999d3de54ce25ba6e389eaeb1273f4f@dismail.de>

Hi,

> I am going to try to start cherry picking uncontroversial and non failing patches on the python-team branch on to master and removing them from the python-team branch in order to reduce the size of the branch. I can then remove those commits from the python-team branch and force push to update it. What do you think of this approach before I attempt it? I'll wait on your guidance before doing this.

please go ahead. Divide and conquer is imo a good approach to get this branch merged. 

> Another approach I can take is to break the branch apart into 2 or 3 smaller topic branches and make requests for those branches to merge one at a time.

I’m splitting of the build-system-related changes into the
pyproject-build-system branch (again), because these are relatively
self-contained and thus easy to merge into master.

Lars





  parent reply	other threads:[~2024-06-30  7:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  8:24 [bug#71408] Request for merging "python-team" branch Christopher Baines
2024-06-08 14:27 ` Ludovic Courtès
2024-06-08 21:04   ` Sharlatan Hellseher
2024-06-18 20:46 ` jgart via Guix-patches via
2024-06-19  7:28   ` Tanguy LE CARROUR
2024-06-19 13:45   ` Christopher Baines
2024-06-25 17:04     ` jgart via Guix-patches via
2024-06-25 18:06       ` Sharlatan Hellseher via Guix-patches
2024-09-24  7:25         ` Steve George
2024-06-30  7:31       ` Lars-Dominik Braun [this message]
2024-06-30  9:42       ` Christopher Baines
2024-09-18  9:09 ` [bug#71408] Postpone? Andreas Enge
2024-09-27  7:30   ` bug#71408: Postpone? Andreas Enge
2024-09-24 13:31 ` [bug#71408] Request for merging "python-team" branch Arseniy Zaostrovnykh
2024-09-26 21:54 ` [bug#71408] Update on Python team pt1 Steve George

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=ZoEJ2Fhf-XLeGSsu@noor.fritz.box \
    --to=lars@6xq.net \
    --cc=71408@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    --cc=marius@gnu.org \
    --cc=me@bonfacemunyoki.com \
    --cc=ngraves@ngraves.fr \
    --cc=sharlatanus@gmail.com \
    --cc=tanguy@bioneland.org \
    /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).