is the "task" concept available in SubVersion?

[Richard & Alex Malcolm <th...@hotmail.com>]

Hi,

I am just wondering if there is the concept of a "task" in SubVersion. What 
i mean by "task" is the association of a set of changes you may perform to a 
number of files to make a single fix or add a single new piece of 
functionality. This concept can be powerful for allowing a single "task" (or 
job) to be managable in its own right (i.e. remove that suite of changes 
etc).

Is that possible in SubVersion?

Cheers,
Richard

_________________________________________________________________
E-mail just got a whole lot better. New ninemsn Premium. Click here  
http://ninemsn.com.au/premium/landing.asp


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: is the "task" concept available in SubVersion?

[Ben Collins-Sussman <su...@collab.net>]

On Mon, 2004-02-23 at 22:40, Richard & Alex Malcolm wrote:
> Hi,
> 
> I am just wondering if there is the concept of a "task" in SubVersion. What 
> i mean by "task" is the association of a set of changes you may perform to a 
> number of files to make a single fix or add a single new piece of 
> functionality. This concept can be powerful for allowing a single "task" (or 
> job) to be managable in its own right (i.e. remove that suite of changes 
> etc).
> 
> Is that possible in SubVersion?

Yes, you're describing what most people call a 'changeset', or a
'patch', 'single commit' or whatever.  Subversion's global revision
numbers are simply names of changesets.  You can refer to them by name,
merge them by name, revert them by name, etc.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org