Source Code Control
in [Embedded]
|
From: Petter Gustad on 7 Nov 2006 20:13 "Andy Peters" <Bassman59a(a)yahoo.com> writes: > On Mac OS X, XCode supports Subversion SCC and it works quite well. If you use Emacs the vc interface is the same if you are using CVS, RCS or SCCS as your back-end source code control system. However, there is an addtional cvs-mode on top of CVS. Petter -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
From: toby on 7 Nov 2006 18:30 Henrik [6650] wrote: > "toby" <toby(a)telegraphics.com.au> skrev i en meddelelse > news:1162909264.750932.91420(a)f16g2000cwb.googlegroups.com... > > [Snip lots of good comments about other systems] > > > As for VSS... the definitive summary is: "Visual SourceSafe? It would > > be safer to print out all your code, run it through a shredder, and set > > it on fire." > > (via > > > http://jeremycoenen.com/blog/index.php/archive/subversion-just-plain-rocks/ > > ) > > 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? Frankly the page "Best Practices for Preventing Data Corruption" just doesn't fill me with confidence about the product, especially after a few years using and administering UNIX based systems that simply Just Work, trouble-free. http://msdn2.microsoft.com/en-us/library/ms181079(VS.80).aspx > 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. Which I first saw as part of this document: http://wadhome.org/svn_vs_vss.html The quote is indeed claimed to originate from a Microsfot employee. You'll also find more anecdotes about VSS there. > > I do not ask this to start a war over which is better ... It sure would be nice to know, though, wouldn't it - since we're all using these tools professionally. > > I have never used anything else but VSS, so I cannot say I have a lot of > experience, but I am always eager to learn and hear other opinions. So > please, friends, throw in your horror/success stories. > > Thanking you all in advance. > Henrik
From: toby on 7 Nov 2006 18:48 FreeRTOS.org wrote: > > We also have experienced database corruption and missing source files. One > > chunk of code, fortunately not too vital, went missing for years... > > curiously, when I converted the database to Subversion, it showed up > > again... > > How did you convert the database? I am looking for a way of converting some > ClearCase VOBs to SVN repositories. Also see: http://www.szabgab.com/subversion_vs_xyz.html Some promising links there, including http://www.unix-girl.com/cc2svn/ > > Regards, > Richard. > > + http://www.FreeRTOS.org > + http://www.SafeRTOS.com > for Cortex-M3, ARM7, ARM9, HCS12, H8S, MSP430 > Microblaze, Coldfire, AVR, x86, 8051, PIC24 & dsPIC
From: Grant Edwards on 8 Nov 2006 00:01 On 2006-11-07, toby <toby(a)telegraphics.com.au> wrote: > Frankly the page "Best Practices for Preventing Data > Corruption" just doesn't fill me with confidence about the > product, 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. All network connections are unreliable! Repeait slowly to yourself "a distributed version control system that can be trashed because of a dropped network connection." Anybody with five firing neurons should know that's simply not acceptible -- and not all that hard to avoid! Database people have known how to deal with situations like that for 30 years. But not Microsoft. Sheesh. We're not talking about just the operation in progress being lost. We're talking about the whole database becoming unstable. There's absolutely no excuse for that. Network connections drop all the time. Power fails. Computers crash. (Microsoft sure ought to know that!) People trip over cables and drive cars into telephone poles. Any distributed system that absolutely depends on 100% reliable network connections was designed by an idiot. -- Grant Edwards grante Yow! I HAVE a towel. at visi.com
From: Henrik [6650] on 8 Nov 2006 01:59
"toby" <toby(a)telegraphics.com.au> skrev i en meddelelse news:1162942250.581179.287000(a)b28g2000cwb.googlegroups.com... > > Frankly the page "Best Practices for Preventing Data Corruption" just > doesn't fill me with confidence about the product, especially after a > few years using and administering UNIX based systems that simply Just > Work, trouble-free. > http://msdn2.microsoft.com/en-us/library/ms181079(VS.80).aspx > That is indeed very disturbing. I guess we have had good fortune for this long. But I see the possibility for terrible things to happen in the future to come. I had not googled around or searched for information regarding this issue, but I was just inspired by the original posting. However, all your answers have made me aware that there is something to look at here. And if the solution is stable, and yet cheap/free. I see a winner here. > > 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. > > Which I first saw as part of this document: > http://wadhome.org/svn_vs_vss.html > The quote is indeed claimed to originate from a Microsfot employee. > You'll also find more anecdotes about VSS there. Thank you, informative, amusing (in a strange deathwish kind of way) and scary information. > > > > > I do not ask this to start a war over which is better ... > > It sure would be nice to know, though, wouldn't it - since we're all > using these tools professionally. Ohhh yes, I am all for the knowledge of which tool is better. But plese note the small word "WAR". Unfortunately discussions about tools (especially MS tools) often tend to get out of hand due to peoples consistent disliking of MS, and I didn't want this to be 300 post argument over Bill, his companymethods or anything like that ;-) I just wanted to know the arguments for NOT choosing VSS. And as always you guys have what it takes. Good arguments, links to prove it and personal experience. Thanks a lot. This is why this group is my favourite newsgroup. > > I have never used anything else but VSS, so I cannot say I have a lot of > > experience, but I am always eager to learn and hear other opinions. So > > please, friends, throw in your horror/success stories. > > > > Thanking you all in advance. > > Henrik Say we should change our sourcecode control. What would be a better choice? It does not have to be cheap/free but this is of course good if it is, as I might have more luck getting it through. Also it MUST run on Microsoft Server, since I am not likely to be allowed to change entire company IT-philosophy :-) And if anything exists to convert between this new creature and VSS, it is all the better. I have been searching a little this night but has been kind of confused with all the frontends/tools etc that exist for the various free solutions. So any pointers are welcome. Thank you all for all your valued inputs to this discussion! Best regards Henrik |