unofficial mirror of 
 help / color / mirror / Atom feed
From: Greg Hogan <>
To: Tobias Geerinckx-Rice <>
Subject: [bug#43427] [PATCH] gnu: zstd: Update to 1.4.5.
Date: Tue, 22 Sep 2020 07:22:52 -0400
Message-ID: <> (raw)
In-Reply-To: <87sgbaw2ri.fsf@nckx>

Thanks, T-G-R. I will endeavor to tag for staging and core-updates going forward. Not sure how I missed the prior commit. I may have been looking among patches. Not sure how I missed the git log, and in the future I will be certain to simply check the latest version from each branch.

Would it be feasible to have `guix refresh` consider staging and core-updates when reporting available updates?


> On Sep 22, 2020, at 5:59 AM, Tobias Geerinckx-Rice <> wrote:
> Greg,
> Mathieu Othacehe 写道:
>> The update is already present on core-updates branch,
> Sorry for the duplicate work!  How were you to've known this, you ask?
> $ guix refresh --list-dependent PACKAGE
> or ‘-l’ for short will list the number of rebuilds that a hash change in PACKAGE would trigger.
> If it's higher than 300, the patch belongs on the ‘staging’ or ‘core-updates’ branches instead of ‘master’.  The exact numbers are in the ‘Submitting Patches’ section of the Guix manual.
> In practice, it's not always clear-cut.  A patch that rebuilds fewer than 300 packages but includes IceCat, Ungoogled Chromium, and LibreOffice probably belongs on ‘staging’ regardless.  A patch that rebuilds 350 (fast-building) Perl packages might be OK for master.
> It's good practice to include the branch name (e.g., ‘[PATCH core-updates]’) when submitting patches not suitable for master.
> Kind regards,
> T G-R

      reply	other threads:[~2020-09-22 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 15:11 Greg Hogan
2020-09-22  9:08 ` bug#43427: " Mathieu Othacehe
2020-09-22  9:59   ` [bug#43427] " Tobias Geerinckx-Rice via Guix-patches via
2020-09-22 11:22     ` Greg Hogan [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:

  List information:

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

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

unofficial mirror of 

This inbox may be cloned and mirrored by anyone:

	git clone --mirror guix-patches/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-patches guix-patches/ \
	public-inbox-index guix-patches

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone