From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id 0GvoHObS62KfIwAAbAwnHQ (envelope-from ) for ; Thu, 04 Aug 2022 16:08:38 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id sFTKHObS62LdCwEAauVa8A (envelope-from ) for ; Thu, 04 Aug 2022 16:08:38 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 0204C47EA8 for ; Thu, 4 Aug 2022 16:08:38 +0200 (CEST) Received: from localhost ([::1]:37288 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oJbWe-0002gy-P9 for larch@yhetil.org; Thu, 04 Aug 2022 10:08:36 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:44666) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJNL3-0001Qs-Oi for help-guix@gnu.org; Wed, 03 Aug 2022 18:59:41 -0400 Received: from 3.mo550.mail-out.ovh.net ([46.105.60.232]:39613) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJNL1-0007M4-4r for help-guix@gnu.org; Wed, 03 Aug 2022 18:59:41 -0400 Received: from player759.ha.ovh.net (unknown [10.109.143.72]) by mo550.mail-out.ovh.net (Postfix) with ESMTP id 8C9C521A81 for ; Wed, 3 Aug 2022 22:59:22 +0000 (UTC) Received: from ngraves.fr (unknown [176.166.159.77]) (Authenticated sender: ngraves@ngraves.fr) by player759.ha.ovh.net (Postfix) with ESMTPSA id DE07B2D485C77; Wed, 3 Aug 2022 22:59:19 +0000 (UTC) X-OVh-ClientIp: 176.166.159.77 To: help-guix@gnu.org Cc: ngraves@ngraves.fr Subject: managing waiting patches Date: Thu, 04 Aug 2022 00:59:19 +0200 Message-ID: <87a68lorw8.fsf@ngraves.fr> MIME-Version: 1.0 Content-Type: text/plain X-Ovh-Tracer-Id: 18287147766011978466 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvfedrvddvkedgudekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucenucfjughrpefhvfevufffkfggtgesthdtredttddttdenucfhrhhomheppfhitgholhgrshcuifhrrghvvghsuceonhhgrhgrvhgvshesnhhgrhgrvhgvshdrfhhrqeenucggtffrrghtthgvrhhnpeeugefgtdekvdeujefhfeeggfevjeehfffgjedvteeuheffheegueffhfdttdehheenucfkpheptddrtddrtddrtddpudejiedrudeiiedrudehledrjeejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpohhuthdphhgvlhhopehplhgrhigvrhejheelrdhhrgdrohhvhhdrnhgvthdpihhnvghtpedtrddtrddtrddtpdhmrghilhhfrhhomhepnhhgrhgrvhgvshesnhhgrhgrvhgvshdrfhhrpdhnsggprhgtphhtthhopedupdhrtghpthhtohephhgvlhhpqdhguhhigiesghhnuhdrohhrghdpoffvtefjohhsthepmhhoheehtd Received-SPF: pass client-ip=46.105.60.232; envelope-from=ngraves@ngraves.fr; helo=3.mo550.mail-out.ovh.net X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Thu, 04 Aug 2022 10:08:23 -0400 X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" Reply-to: Nicolas Graves From: Nicolas Graves via X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1659622118; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=Wwx2TiEuga1paoauLeWky1M5LpIZ6VCnQvomJe+lN8U=; b=oXNFhdJYIb2iZgMm/6+FoajA0xtUUM3RgvUBVjTqISGAZRmZ66QBFiRYHFqRlamCTnvU2V bFME2s6VKEbDApBfb7vkYqGjavEAFHqCv59kmL5i6WH5DqGiqKzGzPpitAI+25w9lNec9Z viKEDxp1LdasbnSf5pneEu46Uc3EWRQ8smOo4mKG82qPjjklV8mDPqVaAyV+OCbFLAIok2 LFz+RQLCaRwgAvculGDu7aENW5LDGy5i9G1ncUq5zEkOYnHhNuz5H0Je4iEl0F0tGp2Qss /aRY50UtzuyHC2DaSimfR3a1dieS7+LEAHFjjH2H1WjUWUlvROjshOD6BmWaVA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1659622118; a=rsa-sha256; cv=none; b=OtXGsB5mFCK52q8rTPUkpn7dZHatBPnUZ4r9exy45K1eYdyNYZF16QwBcE/80zGGyVE1xI uXZJ8AR/Yo5JSEJbWxZEuPtk34SQE2Wjce5L9wtvsTq6jrrkh095M9RxpkP/MPXetJ9Omp 8cWF1xbCLquzVVirJxuOYfHKGWHSubHJb+ClYN343ZQvbhnkSD7RCm//tTDNRG88eiEpm3 A3K0rpTaJ0KvANyB5LA4t5655KkIdjjtBkGsLOuL+REGrqFWLVQwr25QC4i4rIaOJwUGpH J7pDiiCZTBGrma65/TJ5K6QDMWl99oxjuJdmH9eTcVtMYgBufk82rTuI/DoCFg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -3.21 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 0204C47EA8 X-Spam-Score: -3.21 X-Migadu-Scanner: scn1.migadu.com X-TUID: xMWLF2RCvigm Hi! I've some patches waiting to be merged, and was thinking about how to deal with that. (I understand that maintainers are few and probably overworked, I'm not criticizing anyone.) There are actually two problems in one : 1) how to manage and track series of patches one makes in his local repo copy. For that, I will take a practical example. I made some rust patches a few days ago. The final goal of these first patches would have been to add the package swayr@0.20, which is huge when imported with recursive guix import (~2k lines). So I did split the task in a few subgoals, by trying to first update packages that are already present. By only doing that, I already had a stack of ~15 commits. I couldn't contribute more at that moment, so I sent them in the hope that they would get merged before a next partial goal. Eventually, I decided to contribute other packages meanwhile, some patches were either merged in the master branch, another one in the staging branch, and other were not. My local copy repo quickly starts to be a mess. It's not too bad for now, but I'm starting to feel the need to get more organized for that. I've thought about a few solutions on a personnal level to tackle that. There of course the option to put commits in a branch, which may be sufficient, and may combine with the package emacs-git-email to provide complete functionality. I've also seen the stacked-git program, which seems more adapted to these workflows. There's a partially functional (unmaintained) magit-stgit (which I liked on paper because of the ability to send series of patches through a magit-popup) and an emacs-stgit package, but is not in guix so I guess no one is using that. Is there a place I can find some best practices about managing series of patches (as a contributor), beyond implementing "The Perfect Setup"? 2) how to get one's patches to pass. Another problematic I encounter is having to wait for a patch series to pass to send another one. Another example. I'm developing in my free time for an organisation using wagtail CMS for its website. I thought that it would be a great occasion to send some packages for guix, and get some experience with packaging. So I worked on that and send some patches (55476 55475 55474 55473). They are pretty clean (almost all tests enabled, tested as a user) (except maybe for descriptions, I'm not sure I remember for that). At some point, wagtail made an upgrade to version 3.0.1, and I started to update my packages locally, but don't want to make a totally new series of patches while the previous was not accepted. In the meantime, I send patches 56296 which would have been useful for later and actually fixes some failing packages. I'm now stuck on this contributing task because of this. I've seldomly sent reminders, but with no answer for now. And don't feel comfortable writing here for this (I'm not actually, I'm only taking concrete examples and searching for better solutions). What should I do in this case? Should I try to become a committer myself? Have a "committer buddy" that can merge my sent packages? Keep working in a personal channel or a channel like guixrus and rely on that additionally to relying on guix? Other options? Thanks a lot for your answer, sorry if I don't have very acute developer workflows, I'm only doing this in my free time ;) -- Best regards, Nicolas Graves