> >Yeah, but there is already junk up there. Why not put something that > >can be used up there? > > Because two wrongs don't make a right IMHO ;)
I see your point. My gripe with everything I think has more to do with the auto-build of the sites. This isn't really the best example, but docs/api/etc should match the releases - and not the head - or at the very least, offer both. In all honesty, I wasn't even familiar with the http://cvs.apache.org/repository until today, otherwise I wouldn't have bothered anyone with this. I do think the email stuff is useful (although a very small library). Glad to see that there is an echo response :-) - Mike > If anything, we should > either remove what's there (which is against iBiblio policy I think, so > can't be done) or add a notice that says the stuff on there is junk and > users should turn to XXX (whatever URL we want) to track development, > and also that when a stable release is available it will be put up in > iBiblio. > > Yoav > > > > This e-mail, including any attachments, is a confidential business communication, > and may contain information that is confidential, proprietary and/or privileged. > This e-mail is intended only for the individual(s) to whom it is addressed, and may > not be saved, copied, printed, disclosed or used by anyone else. If you are not > the(an) intended recipient, please immediately delete this e-mail from your computer > system and notify the sender. Thank you. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
