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

RE: Subversion use case - Remote users with no network connectivi ty

From: Shatzer, Larry <Larry.Shatzer_at_MIROtechnologies.com>
Date: 2005-10-13 02:10:04 CEST

Have a look at SVK... http://svk.elixus.org/

> -----Original Message-----
> From: Gino Filicetti [mailto:gino@filicetti.net]
> Sent: Wednesday, October 12, 2005 5:07 PM
> To: users@subversion.tigris.org
> Subject: Subversion use case - Remote users with no network
> connectivity
>
>
> Hi Guys,
>
> I've had this use case floating around in my head for a while
> now, and
> I wanted to ask this mailing list to see if it is possible to support
> it given what is currently in Subversion.
>
> I've read about exporting repositories, etc... but I'm not sure if
> that would fully support what I'm trying to do.
>
> Here's the situation:
>
> I work in Sales, specifically on the technical sales team. We have
> suite of our own products and product extensions that we've tweaked
> and create a demo environment from. This environment is source
> controlled using Subversion.
>
> Often, we work on site at prospects doing proof of concepts to show
> that our products can be configured to operate as the prospect
> intends. It is during these PoCs that a lot of development happens,
> sometimes reusable, most times very specific to the prospect in
> question but it always starts using our demo environment as a
> baseline.
>
> Of course, we need to use Subversion during these PoCs to make our
> development as efficient as possible, the one caveat is that most
> times we do not have network access from the prospect's
> building. This
> would prevent us from using the main Subversion server back
> at corporate.
>
> So my question is this.... what would be the best way to take a copy
> of the Subversion repository, put it on a laptop or other
> machine that
> we can keep local, on site. Then use that as our repository
> during the
> PoC development? At the end of the development, it is important that
> we be able to bring back our completed work, check it into the main
> repository on a branch, and then do some selective merging to bring
> only the reusable bits back into our trunk for continued use.
>
> Can this scenario be easily supported? I know I can export a
> repository, but what I can't figure out is if it is possible to come
> back weeks later, with this repository and then take it and somehow
> check the new changes into the main repository?
>
> Any help would be appreciated.... let me know if you need
> clarification.
>
> G

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 13 02:14:16 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.