Comments on: Megalomania in Revision Control Systems http://barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/ … and there is much to be learned Thu, 02 Feb 2012 14:46:19 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Peter Williams - Your Next Version Control System http://barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/comment-page-1/#comment-40299 Peter Williams - Your Next Version Control System Sat, 12 Jan 2008 05:53:59 +0000 http://pezra.barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/#comment-40299 <p>[...] week I did some work on a project that uses Subversion and, man, what a difference a year makes. Back then I dreamed of being able use Subversion instead of Perforce. Now using svn feels a bit like walking around waste deep in [...]</p> [...] week I did some work on a project that uses Subversion and, man, what a difference a year makes. Back then I dreamed of being able use Subversion instead of Perforce. Now using svn feels a bit like walking around waste deep in [...]

]]> By: Peter Williams http://barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/comment-page-1/#comment-2637 Peter Williams Mon, 25 Sep 2006 15:17:36 +0000 http://pezra.barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/#comment-2637 <p>Donna, I really have no idea of what we pay for Perforce.</p> Donna, I really have no idea of what we pay for Perforce.

]]> By: Donna http://barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/comment-page-1/#comment-2594 Donna Fri, 22 Sep 2006 18:14:08 +0000 http://pezra.barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/#comment-2594 <p>Hi Peter,</p> <p>Can you give me an approximation of what you pay for Perforce version control at your company. I'm doing a little research for a school project and am trying to get a sense of what these tools cost. I assume a company would pay about $600 / user for the first year and then a reduced cost for maintenance every year there after. Is this a correct assumption?</p> <p>Sincerely, Donna</p> Hi Peter,

Can you give me an approximation of what you pay for Perforce version control at your company. I’m doing a little research for a school project and am trying to get a sense of what these tools cost. I assume a company would pay about $600 / user for the first year and then a reduced cost for maintenance every year there after. Is this a correct assumption?

Sincerely,
Donna

]]> By: John Sequeira http://barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/comment-page-1/#comment-2171 John Sequeira Wed, 23 Aug 2006 01:50:03 +0000 http://pezra.barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/#comment-2171 <p>Or actually WinMerge alone might just do it for you, if external contributor code diff's is the motivation.</p> <p>That's what I use to determine the reverse -- what the client has added since the my last code grab. :-)</p> Or actually WinMerge alone might just do it for you, if external contributor code diff’s is the motivation.

That’s what I use to determine the reverse — what the client has added since the my last code grab. :-)

]]> By: John Sequeira http://barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/comment-page-1/#comment-2170 John Sequeira Wed, 23 Aug 2006 01:37:43 +0000 http://pezra.barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/#comment-2170 <p>Maybe you should look at:</p> <p>http://svk.elixus.org/?MirrorVCP</p> <p>Like a vcs-agnostic tailor ( has p4 support) ... I don't know if it works, but I'm pretty sure p4 was one of the original targets.</p> Maybe you should look at:

http://svk.elixus.org/?MirrorVCP

Like a vcs-agnostic tailor ( has p4 support) … I don’t know if it works, but I’m pretty sure p4 was one of the original targets.

]]> By: Peter Williams http://barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/comment-page-1/#comment-2168 Peter Williams Tue, 22 Aug 2006 23:10:13 +0000 http://pezra.barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/#comment-2168 <p>Oh, I am asking my self that question and I would definitely be better off using an alternative version control system. However, Perforce is the anointed tool here so that is what I have to use and Tailor does not seem to support Perforce.</p> <p>Interestingly, I created p4-status to deal with code drops from an external contractor. I need a way to detect the additions and and deletions he had made since the last drop.</p> Oh, I am asking my self that question and I would definitely be better off using an alternative version control system. However, Perforce is the anointed tool here so that is what I have to use and Tailor does not seem to support Perforce.

Interestingly, I created p4-status to deal with code drops from an external contractor. I need a way to detect the additions and and deletions he had made since the last drop.

]]> By: John Sequeira http://barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/comment-page-1/#comment-2166 John Sequeira Tue, 22 Aug 2006 21:53:02 +0000 http://pezra.barelyenough.org/blog/2006/08/megalomania-in-revision-control-systems/#comment-2166 <p>At this point, if I were you I would be asking myself whether I wouldn't be better off using an alternative version control tool for my source code, and just rsyncing to the p4-controlled directory for checkins.</p> <p>I do this all the time with clients -- I manage stuff in my local VMware instance of their production setup in e.g. darcs, and when I'm ready I push changes 'over the wall' to whatever version control system they prefer.</p> <p>Darcs even has a tool to support this more elegantly than using rsync (tailor) ... ymmv.</p> At this point, if I were you I would be asking myself whether I wouldn’t be better off using an alternative version control tool for my source code, and just rsyncing to the p4-controlled directory for checkins.

I do this all the time with clients — I manage stuff in my local VMware instance of their production setup in e.g. darcs, and when I’m ready I push changes ‘over the wall’ to whatever version control system they prefer.

Darcs even has a tool to support this more elegantly than using rsync (tailor) … ymmv.

]]>