From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Re: About sourceforge - Bug/Patch managers
Date: Sun, 2 Apr 2000 05:52:53 +0000 [thread overview]
Message-ID: <1000402055254.ZM17830@candle.brasslantern.com> (raw)
In-Reply-To: <000101bf9ad8$182785c0$21c9ca95@mow.siemens.ru>
On Mar 31, 10:12am, Andrej Borsenkow wrote:
} Subject: About sourceforge - Bug/Patch managers
}
} Anybody knows, how to use them?
Bug reports appear to be stored in a MySQL database; I don't know if
that means this is SourceForge's home-grown tracking system, or what.
Submitting bugs appears to be pretty straightforward; but only project
admins can change the status of a bug AFAICT, or even generate any kind
of reports about them. Any other developer can only see either all
bugs, or a restricted view of only those bugs assigned to him (and only
50 of those, too -- I suppose they think nobody would ever be asked to
deal with more than that many bugs at once).
If there's any kind of automatic connection between CVS commits/logs
and the bug system, I can't find it.
Submitting a patch looks pretty obvious, too -- but as I'm not an admin
on the project, I can't follow the Admin link to see what can be done
with the patch after it's been uploaded.
It'd be nice if we could have patches (and bug reports) that are posted
to SourceForge get forwarded to zsh-workers automatically.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-04-02 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-31 6:12 Andrej Borsenkow
2000-04-02 5:52 ` Bart Schaefer [this message]
2000-04-02 17:41 ` Peter Stephenson
2000-04-02 18:28 ` Bart Schaefer
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=1000402055254.ZM17830@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).