From: John Kehayias <john.kehayias@protonmail.com>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Andreas Enge <andreas@enge.fr>,
guix-devel@gnu.org, jgart@dismail.de, vivien@planete-kraus.eu,
rekado@elephly.net
Subject: Re: Python feature branch
Date: Tue, 09 May 2023 04:26:32 +0000 [thread overview]
Message-ID: <87a5yeqgen.fsf@protonmail.com> (raw)
In-Reply-To: <ZFkxT8otQRg3eIGY@noor.fritz.box>
Hi all,
On Mon, May 08, 2023 at 07:28 PM, Lars-Dominik Braun wrote:
> Hi Andreas,
>
>> I wanted to set up automatic building on cuirass for the Python updates
>> branch, but was not sure which one it is:
>> $ git branch -a | grep python
>> remotes/origin/python-updates
>> remotes/origin/wip-python-graphviz
>> remotes/origin/wip-python-mne
>> remotes/origin/wip-python-pep517
>
> I doubt there is one yet. Per #63139 I was going to set up
> “python-team”, which seems to be the naming consesus right now.
>
Right, I don't think we have a naming convention, but as per some
other threads we want to solidify this new process over the
staging/core-updates monolithic branches. We could add this as part of
the patch naming convention to ease finding patches and using QA for
testing/building. A straightforward "python-team" or "python-updates"
in general sounds good to me.
By the way, I'll comment in #63139, but I'll be away for several weeks
starting at the end of this week. I'll see what progress I can chip
away at before then and leave it in all these capable hands.
Thanks!
John
next prev parent reply other threads:[~2023-05-09 4:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 6:05 Python feature branch John Kehayias
2023-05-08 16:17 ` Andreas Enge
2023-05-08 17:28 ` Lars-Dominik Braun
2023-05-08 17:38 ` Ricardo Wurmus
2023-05-09 4:26 ` John Kehayias [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-28 18:38 Sharlatan Hellseher
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=87a5yeqgen.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=rekado@elephly.net \
--cc=vivien@planete-kraus.eu \
/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).