From: Mathieu Othacehe <othacehe@gnu.org>
To: Brice Waegeneire <brice@waegenei.re>
Cc: 49133@debbugs.gnu.org
Subject: [bug#49133] [PATCH] lint: Check for leading whitespace in description.
Date: Thu, 08 Jul 2021 16:10:47 +0200 [thread overview]
Message-ID: <87fswox5eg.fsf@gnu.org> (raw)
In-Reply-To: <20210620133419.15883-1-brice@waegenei.re> (Brice Waegeneire's message of "Sun, 20 Jun 2021 15:34:19 +0200")
Hey Brice,
> * guix/lint.scm (check-description-style): Check for leading whitespace.
> * tests/lint.scm: ("description: leading whitespace"): New test.
Looks fine, you can go ahead.
Thanks,
Mathieu
next prev parent reply other threads:[~2021-07-08 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 13:34 [bug#49133] [PATCH] lint: Check for leading whitespace in description Brice Waegeneire
2021-07-08 14:10 ` Mathieu Othacehe [this message]
2021-07-13 5:26 ` bug#49133: " Brice Waegeneire
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=87fswox5eg.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=49133@debbugs.gnu.org \
--cc=brice@waegenei.re \
/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.