From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: Leo Famulari <leo@famulari.name>, Guillaume Le Vaillant <glv@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: Making `python-next` the next `python`
Date: Tue, 09 Nov 2021 08:38:12 +0100 [thread overview]
Message-ID: <1636443313.uccndk3iap.astroid@melmoth.none> (raw)
In-Reply-To: <YYlB+g2/QtTNYQQO@jasmine.lan>
Hi Guillaume, hi Leo,
Excerpts from Leo Famulari's message of November 8, 2021 4:27 pm:
> On Mon, Nov 08, 2021 at 10:58:40AM +0100, Tanguy LE CARROUR wrote:
>> Just to make sure I don't ask any other stupid questions in the future,
>> where am I supposed to get this information from? I mean, I checked
>> `guix-devel` before posting, but could not find any mention to this topic.
>
> You have to deduce it based on some knowledge about what kind of
> packages can be updated on the master branch and what kind of packages
> cannot be updated there.
> […]
> Then, you can check out the core-updates branch and see if the update
> has been performed there. As we are in the final stages of the
> core-updates cycle, there is also a core-updates-frozen branch, and even
> a core-updates-frozen-batched-changes branch... to learn about those,
> you'd have to ask on IRC or guix-devel.
>
> I hope that helps!
Very helpful indeed! Thanks guys for taking the time to answer!
Best regards,
--
Tanguy
prev parent reply other threads:[~2021-11-09 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 8:50 Making `python-next` the next `python` Tanguy LE CARROUR
2021-11-08 9:26 ` Guillaume Le Vaillant
2021-11-08 9:58 ` Tanguy LE CARROUR
2021-11-08 10:15 ` Guillaume Le Vaillant
2021-11-08 15:27 ` Leo Famulari
2021-11-09 7:38 ` Tanguy LE CARROUR [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
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=1636443313.uccndk3iap.astroid@melmoth.none \
--to=tanguy@bioneland.org \
--cc=glv@posteo.net \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).