I missed no commit mails the last days. Maybe they were declared as spam by your mail filter software?
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: George Aroush [mailto:geo...@aroush.net] > Sent: Saturday, August 29, 2009 10:36 PM > To: java-dev@lucene.apache.org > Subject: RE: Porting Java Lucene 2.9 to Lucene.Net > > I have been watching SVN commits for about 2-3 weeks now (since the > announcement that the trunk was going to be an RC) during this time, I > have > not received any email. It was emails from JIRA that hinted me at code > checkin's. > > -- George > > -----Original Message----- > From: Mark Miller [mailto:markrmil...@gmail.com] > Sent: Saturday, August 29, 2009 11:56 AM > To: java-dev@lucene.apache.org > Subject: Re: Porting Java Lucene 2.9 to Lucene.Net > > George Aroush wrote: > >>> while I'm subscribed to SVN's commits mailing list, I'm not getting > >>> all those commits! For example, a commit made this past Friday, I > >>> never got an email for, while other commits I do. Any idea what > >>> maybe going on? > >>> > >> There has been some flakiness with ASF servers, so maybe that is the > >> reason? Are you using forwarding on people.a.o? > >> > > > > No, I'm not using any forwarding. > > > > If the code, in the truck, goes through minimal changes for about 2 > weeks, > I > > should be fine (until when we figure out the mail issue). > > > > -- George > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > > Have you noticed it happen more than the one time? I've seen similar odd > drops on the reg mailing list rarely - a random reply will show up to an > original email I never got. Didn't notice it happen enough to claim its > anything but bad luck though ;) It makes me wonder what I've missed and > not realized though. I'm not forwarding either. > > bq. If the code, in the truck, goes through minimal changes for about 2 > weeks, > > It should be fairly stable over the next week - bug fixes, build issues, > and > doc are still fair game, but it should be quite contained and rarely > involve > code changes (knock on wood). When we unfreeze, there is likely to be > rapid > development moving towards 3.0 - we will branch off 2.9 before that > though, > and you will probably want to move from trunk to the branch. > > > -- > - Mark > > http://www.lucidimagination.com > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
