I attended a presentation by the core people in the VB.NET team last
summer and the topic of VSS came up. They said they don't use VSS
internally. I can't remember what they said they did predominantly use,
but it was a commercial tool like Perforce.
-----Original Message-----
From: Vaigl, James @ AS [mailto:James.Vaigl@L-3com.com]
Sent: Friday, January 07, 2005 10:46 AM
To: users@subversion.tigris.org
Subject: RE: looking for references on the evil that is VSS
Sean Laurent [mailto:sean@neuronfarm.com] Wrote:
>On Thursday 06 January 2005 05:02 pm, Peter A. Pociask wrote:
>> >Microsoft does not use VSS for their own internal development.
>>
>> Is this true or just an urban legend? I have never been able to find
a
>> confirmation..
>
>True.
>
[...]
>They stated
>that during the Win95 development cycle they utilized a tool known
>as "slime" (aka SLM - Source Library Management), which appeared to
>be a crappy version of CVS >with limited or non-existant
>branching/tagging support.
I can corroborate that. I used an early version of SLM at Microsoft
in '89-'90 when I was in their OS/2 OEM program working for NCR.
That was all they were using as far as I could tell. And it only
ate my hard drive twice in three weeks. Oh, and once afterward.
--Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 7 17:25:46 2005