From: John Cole <john.cole@ua...> - 2004-06-30 12:42:36
First, let me say that it's both surprising and pleasing that t=
has perked up. I had forgotten that I had subscribed to it lon=
g ago :-)
I have seen that other development oriented lists often se=
through, and in fact, that is the only way I have ever had pa=
I have created feature requests on the mantis bugtracker=
patches to implement those feature requests in the past, a=
nd I don't think
they have ever had their state changed from 'new'.
If there is going to be a web based system, I would hope that it would b=
a mantis system itself, as I'm very familiar with that program :-) Bu=
having patches go through the dev list would not bother me at all.
My 2 cents, and it's great to see the activity on the list!
[mailto:mantisbt-dev-admin@...]On Behalf Of Vol=
Sent: Wednesday, June 30, 2004 12:06 AM
Subject: Re: [Mantisbt-dev] Development Discussions
Jacob Coby <jacob.coby@...> writes:
>> > I am thinking we eve=
n send patches to be reviewed to the mailing list
>> > as well.
This, not so much. Perhaps a separate list? But I don't want to wade
though patches to read the tid-bits that are of interest to me.
separate list for patches? That seems weird. As long as they're
t as attachments, not inline, and aren't larger than a few KB
> each, I=
don't see any problems.
I agree. But on the other hand, how about a w=
eb-based "patch archive"
where people can submit patch files they find u=
* Volker Wegert * http://www.volker-wegert.de=
* "Reue ist der feste Vorsatz, beim n=C3=A4chsten Mal keine F=
* hinterlassen." (Marcel Achard)
This SF.Net email s=
ponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings &=
Training, Las Vegas July 24-29 -
digital self defense, top technical e=
xperts, no vendor pitches,
unmatched networking opportunities. Visit ww=
-dev mailing list
This email and any files transmitted with it are confidential an=
d intended solely for the use of the individual or entity to whom they ar=
e addressed. If you have received this email in error please notify the s=
ystem manager. This message contains confidential information and is inte=
nded only for the individual named. If you are not the named addressee yo=
u should not disseminate, distribute or copy this e-mail.