unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Z572 <zhengjunjie@iscas.ac.cn>
To: Cayetano Santos <csantosb@inventati.org>
Cc: 73837@debbugs.gnu.org
Subject: [bug#73837] [PATCH] gnu: iverilog: Update to 12.0.
Date: Wed, 16 Oct 2024 20:56:57 +0800	[thread overview]
Message-ID: <8734kw4352.fsf@iscas.ac.cn> (raw)
In-Reply-To: <87cyk08b9k.fsf@inventati.org> (Cayetano Santos's message of "Wed, 16 Oct 2024 14:47:51 +0200")

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

Cayetano Santos <csantosb@inventati.org> writes:

>>mer. 16 oct. 2024 at 20:20, Z572 <zhengjunjie@iscas.ac.cn> wrote:
>
>> Cayetano Santos via Guix-patches via <guix-patches@gnu.org> writes:
>
>> It is best to use git send-email, see
>
> I’m using send-email (?)

Not sure why some people send emails containing patch that are not sent from their own mailbox

e.g.
Cayetano Santos via Guix-patches via <guix-patches@gnu.org>



>
>> And without them, build also success.
>
> There is just a couple of warnings:
>
>   warning: no binary for interpreter `perl' found in $PATH
>   warning: no binary for interpreter `csh' found in $PATH
>
> I included perl and tcsh to avoid these.

In general, they may be needed for development scripts, so packaging
does not require them. If packaging fails, you can pay attention to see
if there is a lack of dependencies here

>
>> here is patch after the modification.
>
> Other than the warnings, fine with me. Any action from my side ?

If there is no problem, I will push it to the warehouse later

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2024-10-16 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16 10:19 [bug#73837] [PATCH] gnu: iverilog: Update to 12.0 Cayetano Santos via Guix-patches via
2024-10-16 12:20 ` Z572
2024-10-16 12:47   ` Cayetano Santos via Guix-patches via
2024-10-16 12:56     ` Z572 [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=8734kw4352.fsf@iscas.ac.cn \
    --to=zhengjunjie@iscas.ac.cn \
    --cc=73837@debbugs.gnu.org \
    --cc=csantosb@inventati.org \
    /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).