From: Christopher Baines <mail@cbaines.net>
To: Simon South <simon@simonsouth.net>
Cc: 43915@debbugs.gnu.org
Subject: [bug#43915] [PATCH 0/3] Update python-breathe and dependencies
Date: Fri, 23 Oct 2020 22:48:03 +0100 [thread overview]
Message-ID: <87y2jw1ung.fsf@cbaines.net> (raw)
In-Reply-To: <87ft6llnra.fsf@simonsouth.net>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
Simon South <simon@simonsouth.net> writes:
> Simon South <simon@simonsouth.net> writes:
>> Note "guix refresh --list-dependent" reports that python-breathe,
>> python-sphinx and python-six have 1, 363 and 6,538 dependent packages,
>> respectively.
>
> ...and as soon as I hit "send" I notice this in the Guix manual:
>
> ...if your patch is to be applied on a branch other than ‘master’,
> say ‘core-updates’, specify it in the subject like ‘[PATCH
> core-updates] ...’.
>
> I can resend if desired, and I'll follow this convention in the future.
No problem :)
I've pushed the python-six change to the core-updates branch as
6f95911ad175a836fbd5aaa42a8aecb0fc335a1e.
Given the python-sphinx change is a major version update, I was unsure
about pushing it to master, at least without testing whether any of the
363 dependent packages are broken by this change.
I think the staging branch is also frozen. I'll investigate tomorrow
about starting a new staging branch...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2020-10-23 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 22:21 [bug#43915] [PATCH 0/3] Update python-breathe and dependencies Simon South
2020-10-10 22:24 ` [bug#43915] [PATCH 1/3] gnu: python-six: Update to 1.15.0 Simon South
2020-10-10 22:24 ` [bug#43915] [PATCH 2/3] gnu: python-sphinx: Update to 3.2.1 Simon South
2020-10-10 22:24 ` [bug#43915] [PATCH 3/3] gnu: python-breathe: Update to 4.22.1 Simon South
2020-10-10 22:28 ` [bug#43915] [PATCH 0/3] Update python-breathe and dependencies Simon South
2020-10-23 21:48 ` Christopher Baines [this message]
2020-10-23 22:39 ` Simon South
2020-10-24 20:17 ` Christopher Baines
2020-12-18 14:27 ` bug#43915: " Simon South
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=87y2jw1ung.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=43915@debbugs.gnu.org \
--cc=simon@simonsouth.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.