From: zimoun <zimon.toutoune@gmail.com>
To: Brett Gilio <brettg@gnu.org>
Cc: Evan Straw <evan.straw99@gmail.com>, 44725-close@debbugs.gnu.org
Subject: bug#44725: ocaml-cairo2 package fails to build
Date: Thu, 19 Nov 2020 23:09:15 +0100 [thread overview]
Message-ID: <86pn49xalw.fsf@gmail.com> (raw)
In-Reply-To: <87ft55uoxk.fsf@debian>
Hi Brett,
Thank you for the fix.
On Thu, 19 Nov 2020 at 13:28, Brett Gilio <brettg@gnu.org> wrote:
>> [0]
>> https://github.com/kit-ty-kate/opam-repository/commit/4db9f97d242fbfd3b3100128797a4f941f66a32d
>>
>> [1] https://github.com/ocaml/ocaml/issues/9360
This commit message of 34ba163718513f8962e14e325a109110a83bdf1c reads:
--8<---------------cut here---------------start------------->8---
* gnu/packages/ocaml.scm (ocaml-cairo2): Amend comment about tests.
Related to issue #44725.
--8<---------------cut here---------------end--------------->8---
Usually, the standards instead of “Related to issue #44725” is:
--8<---------------cut here---------------start------------->8---
Fixes <https://bugs.gnu.org/44725>.
Reported by Evan Straw <evan.straw99@gmail.com>
--8<---------------cut here---------------end--------------->8---
The “Fixes” could be replaced by “This fixes” or “Related to” or any
other relevant message. The important part is “https://bugs.gnu.org”
which is really helpful for grepping the history: walking back to find
why something or processing some stats when releasing. (Since the bug
tracker is not really connected to the commit tree.)
All the best,
simon
prev parent reply other threads:[~2020-11-19 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 18:32 bug#44725: ocaml-cairo2 package fails to build Evan Straw
2020-11-18 21:53 ` Brett Gilio
2020-11-19 8:56 ` zimoun
2020-11-19 19:24 ` Brett Gilio
2020-11-19 19:28 ` Brett Gilio
2020-11-19 22:09 ` zimoun [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=86pn49xalw.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=44725-close@debbugs.gnu.org \
--cc=brettg@gnu.org \
--cc=evan.straw99@gmail.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 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).