public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Alex Schuilenburg <alexs@ecoscentric.com>
To: ecos-maintainers@sources.redhat.com
Subject: Bug submission and comments via emal
Date: Fri, 08 Aug 2003 15:42:00 -0000	[thread overview]
Message-ID: <3F33C4F2.40000@ecoscentric.com> (raw)

eCos Maintainers,

I have fixed the bugzilla email interface (broken my the bugzilla 
maintainers in the move from 2.16 to 2.17). You can now submit bug 
reports and comments to bugs via email to bugzilla.  This includes 
attachments which are stored as attachments.

There is one big caveat:  you must submit the bug or comment from the 
same email account that you hold for bugzilla.

The email account to submit bugs/comments via email is 
<bugmail@ecoscentric.com>.

Instructions for creating bugs are at:
   http://bugzilla.ecoscentric.com/contrib/bugmail_help.html

If you wish to comment on a bug, send email to the same email address 
with the subject line containing "[Bug 1000044]"  (obviously replace 
1000044 with the actual bug ID.  Anything else on the subject line is 
added to the comment with "Subject: xxx".

Attachments (including multiple attachments) are store automagically 
with new and comment emails.

Upon a new bug submission, you will get email confirming the bug id as 
well the standard bugzilla email.  Consistency checking is performed so 
if you select a product, os, component etc that does not exist, you will 
be alerted via email as to the valid values.  A "@groupset = eCos" will 
make the bug visible to maintainers only.

For bug comments, you will only get regular bugzilla email.

Have fun
-- Alex



                 reply	other threads:[~2003-08-08 15:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F33C4F2.40000@ecoscentric.com \
    --to=alexs@ecoscentric.com \
    --cc=ecos-maintainers@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).