From: 宋文武 <iyzsong@envs.net>
To: Christopher Baines <mail@cbaines.net>
Cc: iyzsong@member.fsf.org, guix-devel@gnu.org
Subject: Re: branch master updated: gnu: w3m: Update to 0.5.3+git20230121.
Date: Wed, 01 Feb 2023 09:35:40 +0800 [thread overview]
Message-ID: <87leliw4k3.fsf@envs.net> (raw)
In-Reply-To: <87357r3vo9.fsf@cbaines.net> (Christopher Baines's message of "Tue, 31 Jan 2023 09:20:37 +0000")
Christopher Baines <mail@cbaines.net> writes:
> guix-commits@gnu.org writes:
>
>> This is an automated email from the git hooks/post-receive script.
>>
>> iyzsong pushed a commit to branch master
>> in repository guix.
>>
>> The following commit(s) were added to refs/heads/master by this push:
>> new a3b57e57e6 gnu: w3m: Update to 0.5.3+git20230121.
>> a3b57e57e6 is described below
>>
>> commit a3b57e57e68a1f4848bf8bacd797c5d989f56de2
>> Author: André Batista <nandre@riseup.net>
>> AuthorDate: Fri Jan 27 09:37:02 2023 -0300
>>
>> gnu: w3m: Update to 0.5.3+git20230121.
>>
>> * gnu/packages/w3m.scm (w3m): Update to 0.5.3+git20230121.
>>
>> Signed-off-by: 宋文武 <iyzsong@member.fsf.org>
>> ---
>> gnu/packages/w3m.scm | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> Given the +1800 dependent packages, the contributing guidance suggests
> this change should go to the core-updates branch.
>
> → guix refresh -l w3m
> Building the following 984 packages would ensure 1859 dependent packages
> are rebuilt: ranger@1.9.3 ...
oops, I forget to check its dependent, think the only one is
emacs-w3m... Sorry for the troubles!
prev parent reply other threads:[~2023-02-01 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167514521744.22195.932934994721635077@vcs2.savannah.gnu.org>
2023-01-31 9:20 ` branch master updated: gnu: w3m: Update to 0.5.3+git20230121 Christopher Baines
2023-01-31 16:35 ` Leo Famulari
2023-01-31 23:18 ` kiasoc5
2023-02-01 1:35 ` 宋文武 [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=87leliw4k3.fsf@envs.net \
--to=iyzsong@envs.net \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.org \
--cc=mail@cbaines.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 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).