From: Greg Hogan <code@greghogan.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 60042@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#60042] [PATCH] gnu: git: Update to 2.39.0.
Date: Tue, 20 Dec 2022 11:38:40 -0500 [thread overview]
Message-ID: <CA+3U0ZmV=50kpOgRGwKnjFA2471O9duKdTJrqdLOZAiQJjeuWQ@mail.gmail.com> (raw)
In-Reply-To: <87edsu6sbp.fsf_-_@gnu.org>
On Tue, Dec 20, 2022 at 9:52 AM Ludovic Courtès <ludo@gnu.org> wrote:
> According to figures in the manual, it’s for ‘staging’ (info "(guix)
> Submitting Patches"). But I guess those figures are less appropriate
> now that the package collection and build farms have grown. We’ll have
> to think about it!
I closed this ticket after noticing that Tobias had hotfixed the
update to the staging branch.
In addition to potentially increasing the dependent package
thresholds, we should consider alternatives to the process for
submitting, reviewing, and testing the patches for staging and
core-updates. I think just having an announced window for submissions
(perhaps 1 week for staging and 2 weeks for core-updates) would
eliminate some unnecessary work. There would be little benefit to
submitting simple package updates before the open window when an even
newer release may still become available. Also, this could encourage
more participation in the validation and testing process: similar to
how releases are branched off master, we could encourage developers
and users to test the pre-merge staging and (especially) core-updates.
next prev parent reply other threads:[~2022-12-20 18:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:40 [bug#60042] [PATCH] gnu: git: Update to 2.39.0 Greg Hogan
2022-12-15 11:35 ` zimoun
2022-12-15 18:55 ` bug#60042: " Greg Hogan
2022-12-20 14:52 ` [bug#60042] " Ludovic Courtès
2022-12-20 15:38 ` Simon Tournier
2022-12-23 23:51 ` [bug#60042] Julia dependency on Git Ludovic Courtès
2022-12-30 13:15 ` zimoun
2023-01-03 17:59 ` Leo Famulari
2023-01-06 22:55 ` [bug#60042] What to call pinned package versions Ludovic Courtès
2023-01-09 10:32 ` Simon Tournier
2023-01-11 13:19 ` Simon Tournier
2023-01-11 17:27 ` Ludovic Courtès
2023-01-11 17:26 ` Ludovic Courtès
2023-01-26 16:45 ` zimoun
2022-12-20 16:38 ` Greg Hogan [this message]
2022-12-25 16:18 ` [bug#60042] [PATCH] gnu: git: Update to 2.39.0 Ludovic Courtès
2023-02-17 15:55 ` [bug#60042] open branches with target merge dates (was Re: [bug#60042] [PATCH] gnu: git: Update to 2.39.0.) Simon Tournier
2023-02-20 11:02 ` Ludovic Courtès
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='CA+3U0ZmV=50kpOgRGwKnjFA2471O9duKdTJrqdLOZAiQJjeuWQ@mail.gmail.com' \
--to=code@greghogan.com \
--cc=60042@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).