All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15976] .hash file requires newline to process correctly
Date: Sat, 09 Mar 2024 18:58:13 +0000	[thread overview]
Message-ID: <bug-15976-163-PcjG8hHFyb@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15976-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15976

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
masonwardle, All,

Thanks for the report.

> I have a <package-name>.hash file with [...]
> I failed to put a newline at the end of the file.

We do have a .editorconfig file at the root of the Buildroot tree,
that instructs text editors to always "insert_final_newline", as
it is customary for UNIX-style text files.

What is your text editor? Can you configure it to respect the
.editorconfig directives?

> this could be addressed in the documentation

Yes, it would be nice to have a patch that points to the existing
.editorconfig, and points to the documentation on how to configure
usual rext editors: https://editorconfig.org/#pre-installed

Would you like to send such patch, please?

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-03-09 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 16:01 [Buildroot] [Bug 15976] New: .hash file requires newline to process correctly bugzilla
2024-03-09 18:12 ` [Buildroot] [Bug 15976] " bugzilla
2024-03-09 18:58 ` bugzilla [this message]
2024-06-15 15:24 ` bugzilla

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=bug-15976-163-PcjG8hHFyb@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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.