From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] links: bump to version 2.20
Date: Fri, 13 Sep 2019 23:15:11 +0200 [thread overview]
Message-ID: <20190913211510.GA25187@x230> (raw)
In-Reply-To: <20190913215626.49c15f1e@windsurf.home>
Hi Thomas,
> Applied to master, thanks. One minor nit: we like to have commit titles
> that are prefixed by "package/links:" instead of just "links:".
Thanks a lot and sorry that I keep forgetting it.
> Another possible improvement to this package is to add a hash for the
> license file in links.hash.
Again, keep forgetting :). I've sent a patch.
> Thanks!
> Thomas
Kind regards,
Petr
prev parent reply other threads:[~2019-09-13 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 20:02 [Buildroot] [PATCH] links: bump to version 2.20 Petr Vorel
2019-09-13 19:56 ` Thomas Petazzoni
2019-09-13 21:15 ` Petr Vorel [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=20190913211510.GA25187@x230 \
--to=petr.vorel@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox