public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001856] how can i use bugzilla account Date: Mon, 03 Jun 2013 14:25:00 -0000 [thread overview] Message-ID: <bug-1001856-777-Tu5VnEmUGn@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001856-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001856 Alex Schuilenburg <alexs@ecoscentric.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |alexs@ecoscentric.com Resolution|--- |NOTABUG --- Comment #1 from Alex Schuilenburg <alexs@ecoscentric.com> --- SunTong, You are referring to the eCosPro developer's kit portal which is only relevant to eCosCentric support customers and is a paid-for service. If you are a paid-for eCosCentric support customer, you are required to login to the eCosPro developer's kit portal using your registered company email address to access the facilities provided therein. bugs.ecos.sourceware.org is used for submitting issues related to eCos. bugzilla.ecoscentric.com is used for submitting issues related to eCosPro. As you obviously have discovered, you can freely use the former to submit issues, although they must be related to the eCos operating system. HTH -- Alex -- You are receiving this mail because: You are the assignee for the bug.
next prev parent reply other threads:[~2013-06-03 14:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-03 13:21 [Bug 1001856] New: " bugzilla-daemon 2013-06-03 14:25 ` bugzilla-daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2013-06-03 13:21 bugzilla-daemon 2013-06-03 14:25 ` [Bug 1001856] " bugzilla-daemon
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-1001856-777-Tu5VnEmUGn@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).