This was more a general reminder because we are seeing more and more cross-posts between the Derby lists.
Sometimes a cross-post may be appropriate -- people need to decide on a case by case basis. Even then, my own personal style would be to post separately to each list to prevent responses from being cross-posted. The problem isn't so much the initial post, but when lengthy threads result in duplicates to all lists. -jean Sanket Sharma wrote: > Hi, > > I don't think it was a cross post at all! The idea was to get some > feedback and opinion from Derby users regarding the features which > they would like to see in coming versions of Derby!! > It was an attempt to get users to speak up about their choices > and demands! > A requirement specification is as critical for users as it is for > developers! > > Infact, I would like to request you to look at the document and put > your comments about what features you would like to see in a > management extension and let me know if I have missed anything!! > > > > Best Regards, > > Sanket Sharma > > > > On 6/14/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: > >> Choose the list that is most appropriate and post there -- you can >> always switch lists later if it seems appropriate. >> >> It's easy to perpetuate a cross-post by responding to a post -- I know I >> don't always catch the cross-posts. Try to drop the additional list(s) >> in your reply if you can. >> >> More good tips are here: >> >> http://www.apache.org/dev/contrib-email-tips.html >> >> -jean >>
