From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13386] New: Freelance VOIP Engineer
Date: Wed, 16 Dec 2020 16:47:48 +0000 [thread overview]
Message-ID: <bug-13386-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13386
Bug ID: 13386
Summary: Freelance VOIP Engineer
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: hithyshi000 at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
VoIP engineer to conduct your Polycom VoIP phones deployment, then look no
further than FieldEngineer. By using our platform, you will be able to access a
pool of highly-qualified VoIP engineers who can complete the work to an
excellent standard, and with minimal hassle for your business.
https://www.fieldengineer.com/c1/deployment-of-polycom-voip-phones
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-12-16 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 16:47 bugzilla at busybox.net [this message]
2020-12-16 16:48 ` [Buildroot] [Bug 13386] Freelance VOIP Engineer bugzilla at busybox.net
2020-12-21 9:37 ` 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-13386-163@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.