all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: jgart via Guix-patches via <guix-patches@gnu.org>
To: 59217@debbugs.gnu.org
Cc: Arun Isaac <arunisaac@systemreboot.net>
Subject: [bug#59217] Acknowledgement ([PATCH] guix: lint: Improve message in linter warning.)
Date: Sat, 12 Nov 2022 09:15:15 -0600	[thread overview]
Message-ID: <20221112091515.GB30032@dismail.de> (raw)
In-Reply-To: <handler.59217.B.166826577117982.ack@debbugs.gnu.org>

On Sat, 12 Nov 2022 15:10:02 +0000 help-debbugs@gnu.org (GNU bug Tracking System) wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.

Hi Arun,

Not sure if you remember that conversation we had about the linter
warning regarding emacs and having to use two spaces in description
field sentences.

Would you mind recapping the issue so that I can improve this message further.

What I wrote is currently vague:

Why do the sentences in the description field have to be separated by two spaces due to Emacs?

all best,

jgart




  parent reply	other threads:[~2022-11-12 15:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12 15:09 [bug#59217] [PATCH] guix: lint: Improve message in linter warning jgart via Guix-patches via
     [not found] ` <handler.59217.B.166826577117982.ack@debbugs.gnu.org>
2022-11-12 15:15   ` jgart via Guix-patches via [this message]
2022-11-22 20:58     ` [bug#59217] Acknowledgement ([PATCH] guix: lint: Improve message in linter warning.) Arun Isaac
2022-11-23 10:13       ` zimoun
2022-11-23 12:52         ` Arun Isaac
2023-03-21 19:50           ` [bug#59217] [PATCH] guix: lint: Improve message in linter warning Maxim Cournoyer
2023-03-22 21:22             ` Arun Isaac
2023-03-23  2:52               ` Maxim Cournoyer
2023-03-22 21:37             ` jgart via Guix-patches via
2022-11-19 18:37 ` Ludovic Courtès

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=20221112091515.GB30032@dismail.de \
    --to=guix-patches@gnu.org \
    --cc=59217@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    --cc=jgart@dismail.de \
    /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.