[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Developing SCC provider - need a better understanding of SVN process flow

From: Hyrum K. Wright <hyrum_at_hyrumwright.org>
Date: Fri, 29 May 2009 21:16:34 -0500

Your question is about using Subversion, not developing it. As such,
it is off topic for this list, and instead belongs on users_at_subversion.tigris.org
.

Cheers,
-Hyrum

On May 29, 2009, at 2:17 PM, Mythgarr wrote:

> After reviewing the largely inadequate list of SCC providers that work
> with SVN, I have decided it would be best to "roll our own" solution.
> This has the added benefit that we can customize it's operation based
> on our in-house needs easily, and it gives me an opportunity to get
> really in-depth with the SVN process flow. I have settled on the
> SharpSVN library primarily due to it's somewhat better documentation,
> although what's there still leaves much to be desired. Hopefully as I
> gain better insight, I can start contributing to the documentation
> efforts.
>
> In dealing with an SVN project (particularly when viewed from the SCC
> perspective), how does "starting" an SVN project work? For instance,
> let's say I have a codebase that I'm migrating to source control. How
> would I inform SharpSVN that I want "C:\\dev\\src\\someproject\\" to
> become the working folder, and that it already contains some files? I
> don't want to, at that point, update or commit. I merely want to make
> updating, committing, and adding an option. It would be similar to
> choosing "Check Out" in TortoiseSVN, but not immediately versioning,
> merging, or modifying the files.
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2356929

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2357044
Received on 2009-05-30 04:16:58 CEST

This is an archived mail posted to the Subversion Dev mailing list.