Re: Simple revision control for working copy

Hello Garrett,

Could you provide a URL for quilt please?
Thanks.

--
Hello Tonio,
In answer to your original question, perhaps what you're looking for is a "backup" solution rather than version control. You could use a script to zip those files that you've modified. The script could be made as simple or as complex as required. The simplest script would just zip your working copy's changed files. The most complex would zip up everything required to recreate your working copy (including base file versions and svn commands). Perhaps there's a script out there already that would do what you want.
If on the other hand, those changes that you're making can be broken down into well-defined incremental development steps, then I'd agree with other replies that you've had, and a short-term private branch might be the solution.
You can also keep a record of prototype work by copying directly from your working copy to a (new) "dead code" private branch. Then you can revert any changes as required and continue development.
--
Rob.
-----Original Message-----
From: Garrett Rooney [mailto:rooneg@electricjellyfish.net]
Sent: 25 September 2006 15:44
To: Tonio
Cc: users@subversion.tigris.org
Subject: Re: Simple revision control for working copy
On 9/25/06, Tonio <toeneeo@yahoo.com> wrote:
>
> Hi,
>
> My normal work flow (probably similar to yours :) ) is
> to make a number of small changes on the working copy
> (saving from IDE each time). Only after a logical unit
> of work is done would I commit this to the repository
> (e.g. made change X).
>
> I don't want/need to save all these little changes to
> the repository each time, but it would be useful to
> have a local revision control "cache" for all these
> little changes, which I might want to revert to, or
> copy some code from.
>
> Probably after each commit to the main repository, I
> would want to delete this cache.
>
> Any recommendations for such a system? (i.e. require
> simple operations like adding to repository, extract,
> without disturbing working of svn)
You might want to look into quilt, although it won't version all the
same things svn does (no moves or copies, for example) it will let you
keep multiple sets of changes to a given file organized until you can
commit them to your repository.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
_____________________________________________________________________
This message has been checked for all known viruses by the MessageLabs Virus Scanning Service, on behalf of Celoxica Ltd.
This email and any files transmitted with it are confidential and 
may be legally privileged. It is intended solely for the use of the 
individual or entity to whom it is addressed. If you have received 
this in error, please contact the sender and delete the material 
immediately. Whilst this email has been swept for viruses, you 
should carry out your own virus check before opening any 
attachment. Celoxica Ltd accepts no liability for any loss or 
damage which may be caused by software viruses or interception 
or interruption of this email.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org