Johannes Luber | 2 May 2009 17:29
Picon
Picon

Re: Why Perforce?

> Perforce outranks all the ones you mention by yards as far as most 
> developers who use it are concerned (well, me at least ;-).

I beg to differ. Perforce is annoying with forcing to check out files before you can edit them, as I tend to
forget to do that. Furthermore I have to lose the current history view, which forces me to remember the
current changeset during the edits and not just between edit sessions.

Another problem is the abyssmal handling of moved files. They lose their history and one cannot diff
between a changeset before the move with one afterwards. So you have to change the revision number
manually. Even subversion does here better. Please tell me, where Perforce has its superiosity compared
to other SCMs.

Johannes

> However, to 
> get a perforce account, you only have to ask. I agree that the perforce 
> people not wanting an open read-only login is a bit of a pain and maybe 
> we should ask them why they want this.
> 
> Also, you can follow the commits on fisheye: 
> http://fisheye2.atlassian.com/browse/antlr which will give you an RSS 
> feed as well.
> 
> Jim
> 
> 
> _______________________________________________
> antlr-dev mailing list
> antlr-dev@...
> http://www.antlr.org/mailman/listinfo/antlr-dev

--

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

Gmane