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

Re: New User - Importing a project with active changes

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: Tue, 5 Feb 2008 13:30:10 +0100


On 05/02/2008, Alan Saunders <ADS_at_tigersolv.com> wrote:
> Hi,
> The development environment here is extremely fluid, with several developers
> working on different (sometimes exclusive, sometimes overlapping) and
> independent developments within the larger project, or simply debugging or
> bug fixing prior to release or on a customer bug report.
> I envisage all bug-fixing operations to be carried out in the Current
> (trunk) area, whilst new features/functionality are carried out in the
> developer areas. As the application is very extensive, and makes great use
> of both common code, and common feature setting areas any of which could be
> changed in a feature development, it is essential that these changes don't
> break either the current branch, or any other developers code. In this
> scenario, each developer would complete his/her work, compilation testing
> etc., make it available for peer review and testing, and when complete merge
> back to the current when it is solid and stable.

Not sure why you bring this up, because it is exactly why you would
create branches inside the repository.

My explanation was aimed at a method you can use to 'import' the
branches after the initial import of 'current' is done: via a
temporary working copy with a checkout of the entire repository.

   // \\  @@     "De Chelonian Mobile"
  / \_/ \/._)    TortoiseSVN
 <\_/_\_/ /      The coolest Interface to (Sub)Version Control
  /_/   \_\      Check out http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-02-05 13:30:23 CET

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

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