all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Efraim Flashner" <efraim@flashner.co.il>,
	"Steve George" <steve@futurile.net>,
	Kaelyn <kaelyn.alexi@protonmail.com>,
	guix-devel@gnu.org
Subject: Re: Core updates status
Date: Thu, 09 May 2024 11:41:16 -0400	[thread overview]
Message-ID: <871q6b2dsz.fsf@gmail.com> (raw)
In-Reply-To: <87seys4qwp.fsf@jpoiret.xyz> (Josselin Poiret's message of "Wed,  08 May 2024 11:03:02 +0200")

Hi Josselin,

Josselin Poiret <dev@jpoiret.xyz> writes:

> Hi Ludo,
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> I’m in favor of whatever allows us to move forward more quickly, so
>> temporarily stashing away the pkgconf changes sounds good to me.
>>
>> In that case, when time permits, could you push a ‘core-updates-new’ (?)
>> branch, (partially) rebased and without the pkgconf changes, and a
>> separate ‘wip-pkgconf’ branch?  Does that seem doable to you?
>
> I did that partially yesterday, moved the old borked core-updates to
> old-core-updates and pushed the cleaned-up version at core-updates.  I
> haven't pushed the pkgconf patches anywhere yet, but we should probably
> focus on c-u for now and worry about that later.

All pkgconf related patches except the one effecting the actual
pkg-config -> pkgconf aliasing should be safe to merge already.

-- 
Thanks,
Maxim


  parent reply	other threads:[~2024-05-09 15:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  6:08 Core updates status Steve George
2024-04-24  9:56 ` Christina O'Donnell
2024-04-24 13:17   ` Steve George
2024-04-24 14:21     ` Christina O'Donnell
2024-04-25 14:06     ` Christina O'Donnell
2024-04-25 14:06       ` bug#40316: " Christina O'Donnell
2024-04-25 17:01       ` nss not reproducible Christina O'Donnell
2024-04-25 18:45 ` Core updates status Kaelyn
2024-04-26 12:56   ` Steve George
2024-04-26 15:58     ` Efraim Flashner
2024-05-05 20:45       ` Josselin Poiret
2024-05-06  2:38         ` Maxim Cournoyer
2024-05-06  8:47           ` Josselin Poiret
2024-05-06 10:21             ` Ludovic Courtès
2024-05-08  9:03               ` Josselin Poiret
2024-05-08 21:42                 ` [PATCH] gnu: glibc: Update patches following upstream's master branch Josselin Poiret
2024-05-14  9:22                   ` Ludovic Courtès
2024-05-09 15:41                 ` Maxim Cournoyer [this message]
2024-05-13  8:49                 ` Core updates status Efraim Flashner
2024-05-08 10:05             ` Andreas Enge
2024-05-08 17:46               ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-05-09 15:38               ` Maxim Cournoyer
2024-05-10  8:08                 ` Andreas Enge
2024-05-13  8:51                 ` Efraim Flashner

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=871q6b2dsz.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=dev@jpoiret.xyz \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    --cc=ludo@gnu.org \
    --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 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.