From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] swupdate: remove empty line
Date: Sun, 14 Jan 2018 19:16:54 +0100 [thread overview]
Message-ID: <1515953814.8426.5.camel@embedded.rocks> (raw)
In-Reply-To: <20180114180339.GC20105@scaer>
Yann,
On Sun, 2018-01-14 at 19:03 +0100, Yann E. MORIN wrote:
> J"org, All,
>
> On 2018-01-14 18:53 +0100, J?rg Krause spake thusly:
> > Reported by Yann E. Morin running:
> >
> > ```
> > $ ./utils/check-package package/swupdate/swupdate.mk
> > package/swupdate/swupdate.mk:42: consecutive empty lines
> > 140 lines processed
> > 1 warnings generated
> > ```
>
> Note: I could have very well done it myself, but by having other do it,
> that spreads the knowledge, and people get used to running it before
> submitting. Or so I hope! ;-)
No problem! Mostly I am running check-package only when submitting a
new package. But, I will try next time to remember of running it every
time :-)
J?rg
next prev parent reply other threads:[~2018-01-14 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 17:53 [Buildroot] [PATCH] swupdate: remove empty line Jörg Krause
2018-01-14 18:03 ` Yann E. MORIN
2018-01-14 18:16 ` Jörg Krause [this message]
2018-01-15 14:19 ` Peter Korsgaard
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=1515953814.8426.5.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=buildroot@busybox.net \
/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.