Source Code Management lets you keep track of different versions of
source code, so that if you introduce a bug at some point, delete a
subroutine you didn't mean to (and save the file), need to rebuild an
older version... the Source Code Management (SCM) system will let you
roll back your changes, or extract all the files as they were at, say,
version 1.2j

There are a few decent free ones - CVS, Subversion / SVN, and Arch /
tla are all open-source. Some of the best Windows clients IMHO for
those are TortoiseCVS and TortoiseSVN - they integrate their SCM
functions right into the Windows Explorer, so they can work with any
application right out of the box (er, ZIP file)

On Thu, 24 Jun 2004 14:27:43 -0500, llile@saltonusa.com
<llile@saltonusa.com> wrote:
>
> Who is WE?  is a good question, Bill.  "We" have a lot of different
> requirements.
>
> The point of the question is to fish for answers like yours, of couse.
>
> >I haven't needed any tools other than those provided by my
> employer.
>
> It is becoming apparent that "my employer" and "me" will soon be one and
> the same, so my employer is developing a shopping list.
>
> What is a source control system and why do I need one?
>
> -- Lawrence Lile
>
> P.S. Just missed a Hakko desolder system on ebay.  It went too cheap! I
> was Out Sniped!
>
> William Chops Westfield <westfw@MAC.COM>
> Sent by: pic microcontroller discussion list <PICLIST@MITVMA.MIT.EDU>
> 06/23/2004 08:22 PM
> Please respond to pic microcontroller discussion list
>
>
>        To:     PICLIST@MITVMA.MIT.EDU
>        cc:
>        Subject:        Re: [EE:] Typical Embedded work requirments
>
>
>
>
> On Jun 23, 2004, at 11:48 AM, llile@SALTONUSA.COM wrote:
>
> > What does it take to actually do what we do?
> >
> Who is "we"?
>
> I've spent 15+ years doing "embedded systems" development, and for most
> of that time I haven't needed any tools other than those provided by my
> employer.  For a while, that wasn't much more than 'access to a system
> that ran the appropriate C compiler, and a test system to run the
> resulting code on, and an appropriate connection between them.'  That
> used to be a Heath-19 terminal accessing a 68k based unix workstation,
> and an ethernet.  But then, I was primarily an embedded SOFTWARE
> engineer; someone else was designing the HW, and they had somewhat
> different requirements...
>
> No one mentioned internet access yet, or a source control utility.
>
> BillW
>
> --
> http://www.piclist.com hint: To leave the PICList
> mailto:piclist-unsubscribe-request@mitvma.mit.edu
>
> --
> http://www.piclist.com hint: To leave the PICList
> mailto:piclist-unsubscribe-request@mitvma.mit.edu
>


--
-Randy Glenn
Computer Eng. and Mgt. Year IV, McMaster University
Chair, McMaster IEEE Student Branch

randy.glenn-at-gmail.com - glennrb-at-mcmaster.ca
randy.glenn-at-computer.org - randy_glenn-at-ieee.org
http://www.randyglenn.ca

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu