From: "Arsen Arsenović via Grub-devel" <grub-devel@gnu.org>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: "Arsen Arsenović" <arsen@aarsen.me>
Subject: Re: Form feed in source code
Date: Thu, 12 Oct 2023 22:49:22 +0200 [thread overview]
Message-ID: <86r0lzwop6.fsf@aarsen.me> (raw)
In-Reply-To: <ZShUZ3lDN7pitdAs@debian>
[-- Attachment #1.1: Type: text/plain, Size: 426 bytes --]
Hi Alex,
Alejandro Colomar <alx@kernel.org> writes:
> I've just downloaded to git repository, and found that there are form
> feeds ('\f') all around the code. Are these on purpose, or are they
> accidental? Would you want a patch for removing them?
See the tail paragraph of
https://www.gnu.org/prep/standards/html_node/Formatting.html
Hope that helps, have a most lovely evening :-)
--
Arsen Arsenović
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
prev parent reply other threads:[~2023-10-12 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 20:17 Form feed in source code Alejandro Colomar
2023-10-12 20:49 ` Arsen Arsenović via Grub-devel [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86r0lzwop6.fsf@aarsen.me \
--to=grub-devel@gnu.org \
--cc=arsen@aarsen.me \
/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.
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.