Fisheye is supposed to be working right now. It probably isn't monitoring the v4 branch though.
Jim > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Yauhen Yakimovich > Sent: Thursday, September 09, 2010 12:39 PM > To: ANTLR-dev Dev > Subject: Re: [antlr-dev] Improvements to the Antlr PHP Target > > Hello Jim, > > We will see where it gets. Looking forward to play with perforce. > I would like to get a login to commit the stable sync later on. > You can use my initials for the handle, i.e. yy. Thanks. > > BTW Since many atlassian products are actively used within ANTLR > project, I was wondering if there any working FishEye access around, so > that one can review the perforce commits? > > On Thu, Sep 9, 2010 at 4:17 PM, Jim Idle <[email protected]> wrote: > > Gents, > > > > If this is going to be an active project (and I hope so!), then you > > should use the ANTLR Perforce directory as this is the definitive SCCS > > - everything else is a mirror and it seems that people set up these > > mirrors and then don't look after them, so they are out of sync. > > Perforce is much better than the other systems anyway ;-) Also, the > > target code will then be built in to the ANTLR tool correctly (there > > is a java class that is invoked by the code generator to give it a > > chance to perform certain things (such as escape > > strings) before the string template is used). > > > > All you need to do is ask on this dev list for a perforce login (just > > need a login name that you want to use). Then install the perforce > > client and follow the getting started text. > > > > -- > With best regards, > Y.Y. > _______________________________________________ > antlr-dev mailing list > [email protected] > http://www.antlr.org/mailman/listinfo/antlr-dev _______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org/mailman/listinfo/antlr-dev
