Hi Aniruddha,
> I've created a new dialog for working with explicit changesets. This
> dialog is similar to the RepoBrowser. The changeset and its
> constituent path names, log message would be stored as a file in some
> predefined folder similar to where the TSVN cache file is stored.
That would mean that they are only available for a single developer
(since they do not reside in the repository). Is that what you want?
> 1. Users can segregate files they are currently working on into
> change-sets for much better bug-fix management. The developer needn't
> sift through all modified files to commit fix for a particular bug -
> just commit that changeset.
I think it would be more in line with SVN common practice to create a
separate branch per bug if the development is to take place
simultaneously.
Developers can easily switch between branches if they want to work on
multiple bugs
> In many environments certain files are
> never committed but modified temporarily for development purposes -
> these can be put into a "Don't commit" changeset.
These files probably should not be versioned if that is the case
(using svn:ignore).
> An initial feedback of the demo from users in our company was very positive.
Were these users experienced SVN users, or are they more experienced
in other version control systems (like CVS, STAT)
> 2. Status and commit for the changeset would be *very* fast.
But there would be no history in the repository about what constituted
a changeset (especially if the bugfix is committed in several stages).
If the local storage is lost, the changeset history is lost as well.
By the way, if you want the changeset concept to be incorporated in
SVN you should discuss this on the SVN user/developer list, not the
TSVN lists (TSVN can only implement what SVN has to offer).
Regards,
Jean-Marc
----------------
___
// \\ @@ "De Chelonian Mobile"
/ \_/ \/._) TortoiseSVN
<\_/_\_/ / The coolest Interface to (Sub)Version Control
/_/ \_\ Check out http://tortoisesvn.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Oct 15 13:29:09 2005