You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by h....@risoe.dk on 2006/04/11 15:31:58 UTC
SVN interface to LabVIEW
We would like to have SVN integrated with LabVIEW.
In order to interface with a revision control system, LabVIEW requires
support of the "Microsoft Common Source Code Control interface".
This seems not to be available in SVN.
Of course we can simply revision the files from outside of LabVIEW as
for any other file, but with integration it would be simpler to use (I
guess).
Anybody know if the "Microsoft Common Source Code Control interface" is
so much dislike the SVN interface that such an interface would be
crippled from its birth?
henning
Re: SVN interface to LabVIEW
Posted by Darko Miletic <da...@uvcms.com>.
h.larsen@risoe.dk wrote:
> We would like to have SVN integrated with LabVIEW.
>
> In order to interface with a revision control system, LabVIEW requires
> support of the “Microsoft Common Source Code Control interface”.
>
> This seems not to be available in SVN.
You need Subversion SCC provider. Currently there are three AFAIK
unfinished projects for that.
Subway
http://nidaros.homedns.org/subway/
SCC lightweight provider
http://chmsubscc.tigris.org/
Subversion SCC provider
http://www.sourcecross.org/projects/index.php
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SVN interface to LabVIEW
Posted by Andy Peters <de...@latke.net>.
h.larsen@risoe.dk wrote:
> We would like to have SVN integrated with LabVIEW.
>
> In order to interface with a revision control system, LabVIEW requires
> support of the "Microsoft Common Source Code Control interface".
>
> This seems not to be available in SVN.
>
> Of course we can simply revision the files from outside of LabVIEW as
> for any other file, but with integration it would be simpler to use (I
> guess).
>
> Anybody know if the "Microsoft Common Source Code Control interface" is
> so much dislike the SVN interface that such an interface would be
> crippled from its birth?
A lot of development apps, incl. Keil's 8051 tools and LabView, have
some kind of built-in support for VSS and Perforce and such.
As a user of both (as well as FPGA tools and MS VC++), I find that I
prefer using TortoiseSVN (and the command line) over using any sort of
integrated source-code control. TortoiseSVN is too good not to use.
-a
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SVN interface to LabVIEW
Posted by Mark Phippard <ma...@softlanding.com>.
h.larsen@risoe.dk wrote on 04/11/2006 11:31:58 AM:
> We would like to have SVN integrated with LabVIEW.
> In order to interface with a revision control system, LabVIEW requires
support
> of the “Microsoft Common Source Code Control interface”.
> This seems not to be available in SVN.
>
> Of course we can simply revision the files from outside of LabVIEW as
for any
> other file, but with integration it would be simpler to use (I guess).
>
> Anybody know if the “Microsoft Common Source Code Control interface” is
so
> much dislike the SVN interface that such an interface would be crippled
from its birth?
Take a look at this commerical product:
http://www.pushok.com/soft_svn.php
They offer an SCC interface.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________