[RFC] Workingstyle of different VCS systems

[Matt Rogers]

On Monday 09 April 2007 14:41, Matthew Woehlke wrote:
> Matt Rogers wrote:
> > On a side note, can we please start calling it SCM (for Source Code
> > Management) rather than VCS? We're not writing KDevelop to handle
> > various versions of things, we're writing it to manage source code.
>
> ...but we are talking about integrating VCS's, not SCMS's. :-)
>
> To me VCS implies it can handle things that are not "source code" (like
> .png's), which of course most if not all of the VCS's we're talking
> about do (take a look at the commits on kde-artists if you don't believe
> me ;-)). This, to me at least, conversely implies that a SCM System
> (i.e. an SCM*S*) does something "more" than a VCS.
>
> You're welcome to try to change my mind. :-)

.pngs are source code in some cases. While I generally agree that VCS and SCM 
are basically interchangable, KDevelop is meant for dealing with _source 
code_ rather than versions of things.
-- 
Matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20070409/8c5ac091/attachment.sig>