From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11141] WF111 package no longer availabe
Date: Tue, 10 Jul 2018 10:25:34 +0000 [thread overview]
Message-ID: <bug-11141-163-pkIYQkun9Z@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11141-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11141
--- Comment #4 from Geert <geert@my-clay.com> ---
Hello Peter,
Thanks for adding the package to the buildroot backup site.
I would love to create a patch.
How can I start: is there a manual that described how you can create patches?
(and thus contributing to Buildroot)? And who's responsible for merging these
into LTS released?
Kind regards,
Geert Visser
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-07-10 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 14:29 [Buildroot] [Bug 11141] New: WF111 package no longer availabe bugzilla at busybox.net
2018-07-10 9:43 ` [Buildroot] [Bug 11141] " bugzilla at busybox.net
2018-07-10 9:57 ` bugzilla at busybox.net
2018-07-10 10:21 ` bugzilla at busybox.net
2018-07-10 10:25 ` bugzilla at busybox.net [this message]
2018-07-10 16:38 ` bugzilla at busybox.net
2018-08-29 20:10 ` bugzilla at busybox.net
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-11141-163-pkIYQkun9Z@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.