Source Code Control
in [Embedded]
|
From: toby on 8 Nov 2006 16:35 Tom Lucas wrote: > "toby" <toby(a)telegraphics.com.au> wrote in message > news:1162909264.750932.91420(a)f16g2000cwb.googlegroups.com... > ... > > - supported by many client tools/plugins on all platforms > > IAR reckons they support systems that conform to the Microsoft SCC > interface - does that include Subversion? To finally answer your question, there is an SCC provider for Subversion: http://www.sourcecross.org/projects/index.php (free download) and Subway, cited here: http://www.projxpert.com/WebHelp/Hosted_Tools_and_Services/Subversion_Version_Control/Reference/Subversion_Clients_Compatible_with_Projxpert.htm (an amazing compendium of Subversion related tools). > Also Rowley's Crossworks > supports Microsoft Visual SourceSafe, SourceGear SourceOffSite 3.5.1 and > CVS so would I be right in assuming that Subversion would be OK too?
From: andrew queisser on 8 Nov 2006 17:16 > I sit here wondering if all this Anti VSS propaganda out there is due to a > general disliking of Microsoft, or does anybody actually have any bad > experiences with Visual Sourcesafe? It seems that nobody (it is not only > in > this newsgroup) has anything nice to say about the product, although no > specifics are listed. Just those "Print your code and set your hair on > fire" > things. > I remember VSS from before it was a MS product and it was bad back then so I don't blame MS for anything. I used to have frequent database corruption on older VSS versions but the one we're using now (6.0d) is fairly stable. The problems I see with VSS in its current incarnation: - Unusable over slower network connections. Our offshore sites either make their own copy of the VSS data (horrible!) or use a product called "source offsite" or something similar. - Limited features. VSS is missing features for anything beyond managing source trees for simple projects with a few users. - Limited to MS users, pretty much. Lots of shared source projects use CVS or Subversion so if you use these types of projects along with Visual Studio and Eclipse projects (I'm describing my situation here) you're better off not using VSS. Andrew
From: ammonton on 8 Nov 2006 17:12 Pete Fenelon <pete(a)fenelon.com> wrote: > Pete Fenelon <pete(a)fenelon.com> wrote: >> repair. Checkins and checkouts would randomly fail. It was impossible to > Actually, and there's another thing. I hate, HATE, *HATE* the > nanny-knows-best exclusive checkout model of VSS. I much prefer the > non-exclusive model in CVS, SVN etc. At work we use VSS without exclusive checkouts. It works, but not great. Occasionally someone writes over someone else's changes, but it's rare. We've also never had corrupt databases or lost data even though the project is several MLOC and there's almost 40 developers banging on it (knock on wood), but almost everyone is fed up with the poor tools and poor performance. Anyway, nowadays Microsoft recommend the new Visual Studio Team System for bigger projects, anyone have any experiences with it? -a
From: Steve at fivetrees on 8 Nov 2006 20:01 "Tom Lucas" <news(a)REMOVE_auto_THIS_flame_TO_REPLY.clara.co.uk> wrote in message news:1162980680.22777.0(a)proxy02.news.clara.net... > "Steve at fivetrees" <steve(a)NOSPAMTAfivetrees.com> wrote in message > news:BImdne48dojaQs3YnZ2dnUVZ8sadnZ2d(a)pipex.net... >> >> Tom, are you in the UK? If so I'd be happy to talk on the phone. Maybe I >> can help... We're using an OpenBSD server for the repo store (on a RAID >> array, backed-up nightly), and it was trivially easy. I imagine a Windows >> installation would be similarly easy, but I've no experience there... > > I certainly am in the UK and I'd be delighted to talk to you about it. I > assume your number on the website is the one to call - when is good for > you? Any time during the day, on the mobile number on the site. Steve (who will organise a chorus of "VSS is shite" in stacked harmonies with the team at work for when the phone rings) http://www.fivetrees.com
From: David Kelly on 8 Nov 2006 21:26
In article <12l2p4fjevr47b(a)corp.supernews.com>, Grant Edwards <grante(a)visi.com> wrote: > This bit is particularly ominous: > > The most common reasons for data corruption are: > > * General network problems, for example, an unreliable > remote connection causing Visual SourceSafe to drop > communication midway through a file check-in. > > That's just un-f*#@king-believable. Why do you find that unbelievable? Is this the first time you have used (or considered using) a Microsoft product? :-( To Microsoft's credit the above is also considered a flaw in CVS which SVN has dealt with. SVN intends to be a better CVS than CVS, not just a different solution for the sake of being different (and incompatible). |