From: Harry Kalogirou <harkal@gmx.net>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: BUG tracker on sourceforge
Date: 29 Apr 2002 11:57:17 +0300 [thread overview]
Message-ID: <1020065115.8446.108.camel@cool> (raw)
Hi all!
I would like to inform you that from now on the BUG tracker on
sourceforge will be maintained and will be _indate_. So that we will be
able to keep track of bugs in more organized way. Bugs are preferably
still posted here, but a record of the bug will be keeped also at
sourceforge so that new developers, hopefully, will contribute by fixing
bugs.
Harry
next reply other threads:[~2002-04-29 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 8:57 Harry Kalogirou [this message]
2002-04-29 21:25 ` BUG tracker on sourceforge Riley Williams
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=1020065115.8446.108.camel@cool \
--to=harkal@gmx.net \
--cc=linux-8086@vger.kernel.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: 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.