all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Tomas Volf <~@wolfsden.cz>
Cc: guix-devel <guix-devel@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: ‘core-updates’ is gone; long live ‘core-packages-team’!
Date: Sun, 15 Dec 2024 17:53:00 +0100	[thread overview]
Message-ID: <87jzc0khw3.fsf@elephly.net> (raw)
In-Reply-To: <8734ipkx6b.fsf@wolfsden.cz> (Tomas Volf's message of "Sun, 15 Dec 2024 12:22:52 +0100")

Tomas Volf <~@wolfsden.cz> writes:

>> Over the years, consensus emerged that ‘core-updates’, as a branch where
>> we lump together all sorts of rebuild-the-world changes, is no longer
>> sustainable.
>
> So, uh, how should I sent patches for that?  Before, I was able to mark
> patches as intended for core-updates.  But since that branch is no more,
> what should I do?  Where should we, non-committers, who do not have a
> dedicated "focused" branch, send patches that cause a lot of rebuilds?

You can still mark them, but instead of using "core-updates" you'd use
whatever team the package relates to.

-- 
Ricardo


      reply	other threads:[~2024-12-15 16:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31 13:03 ‘core-updates’ is gone; long live ‘core-packages-team’! Ludovic Courtès
2024-09-01 16:34 ` Steve George
2024-09-01 17:06   ` Christopher Baines
2024-09-03 14:02     ` Christopher Baines
2024-12-15  3:59     ` Maxim Cournoyer
2024-12-15  8:10       ` Janneke Nieuwenhuizen
2024-12-15 10:39         ` Christopher Baines
2024-12-15 11:16           ` Janneke Nieuwenhuizen
2024-12-15 13:38             ` Christopher Baines
2024-12-15 14:04           ` work-in-progress team branches (was: Re: ‘core-updates’ is gone; long live ‘core-packages-team’!) Maxim Cournoyer
2024-12-15 16:26             ` work-in-progress team branches Christopher Baines
2024-12-15 10:08       ` ‘core-updates’ is gone; long live ‘core-packages-team’! Christopher Baines
2024-09-06  9:01   ` Ludovic Courtès
2024-09-09 15:30     ` Simon Tournier
2024-09-04 12:58 ` Simon Tournier
2024-09-05  8:39   ` Marek Paśnikowski
2024-09-05  9:40     ` Ricardo Wurmus
2024-09-06  9:11   ` Ludovic Courtès
2024-09-06 10:09     ` Andreas Enge
2024-09-06 11:35       ` Marek Paśnikowski
2024-09-06 13:25         ` Andreas Enge
2024-09-06 13:17       ` indieterminacy
2024-09-26 12:52       ` Ludovic Courtès
2024-09-06 17:44     ` Vagrant Cascadian
2024-09-06 18:06       ` Leo Famulari
2024-09-06 20:29         ` Rebasing commits and re-signing before mergeing (Was: ‘core-updates’ is gone; long live ‘core-packages-team’!) Vagrant Cascadian
2024-09-07 17:45           ` Leo Famulari
2024-09-08  2:33             ` Vagrant Cascadian
2024-09-06 19:49       ` ‘core-updates’ is gone; long live ‘core-packages-team’! Christopher Baines
2024-09-09 17:28     ` Naming “build train” instead of “merge train”? Simon Tournier
2024-12-15 11:22 ` ‘core-updates’ is gone; long live ‘core-packages-team’! Tomas Volf
2024-12-15 16:53   ` Ricardo Wurmus [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87jzc0khw3.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=~@wolfsden.cz \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.