all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Zheng Junjie <zhengjunjie@iscas.ac.cn>
To: chris <chris@bumblehead.com>
Cc: 70047@debbugs.gnu.org
Subject: [bug#70047] [PATCH] gnu: highlight: Update to 4.11.
Date: Sun, 31 Mar 2024 12:28:21 +0800	[thread overview]
Message-ID: <87jzljhubz.fsf@iscas.ac.cn> (raw)
In-Reply-To: <ZgiDb_d6QrjZLpUF@guix-xps>

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


chris <chris@bumblehead.com> writes:

> On  3月31日 日, Z572 wrote:
>> 
>> please add more info for commit message
>> 
>
> Z572, the commit is patched with your suggested changes. If you
> believe a different message is needed, feel free to send a specific
> git commit message you think is best and I will amend the commit with
> that :) thank you

Refer to other commits(you can use like 'git log
--grep=this-package-input' to see it), and see
https://www.gnu.org/prep/standards/html_node/Change-Logs.html

It should look something like this.

* gnu/packages/pretty-print.scm (highlight): Update to 4.11.
[source]: Switch to git-fetch.
[home-page]: Switch to html page.
[arguments]<#:make-flags>: Use #$output replace %output.
<#:phases>: Use ‘this-package-input‘ to find lua and perl.


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

  reply	other threads:[~2024-03-31  4:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  9:24 [bug#70047] [PATCH] gnu: highlight: Update to 4.11 chris
2024-03-30  0:11 ` [bug#70047] why use git-fetch chris
2024-03-30 16:24 ` [bug#70047] [PATCH] gnu: highlight: Update to 4.11 Z572
2024-03-30 19:55   ` chris
2024-03-30 21:26   ` chris
2024-03-31  4:28     ` Zheng Junjie [this message]
2024-03-30 20:48 ` chris
2024-03-31  5:58 ` chris
2024-04-30  9:39 ` [bug#70047] [PATCH v2] " Dale Mellor
2024-05-06 12:00   ` bug#70047: " Nicolas Goaziou via Guix-patches via

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=87jzljhubz.fsf@iscas.ac.cn \
    --to=zhengjunjie@iscas.ac.cn \
    --cc=70047@debbugs.gnu.org \
    --cc=chris@bumblehead.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 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.