Re: Tagging changesets

On 8/23/06, John Doisneau <jdoisneau@gmail.com> wrote:
>
> In our company, we are eager to switch to SubVersion (we did not have
> any version control until now) but there could be one functionality
> that we would lose if it is not supported: the possibility of tagging
> changesets.

Can you explain how you manage this now? That is, what functionality
you have that you might lose?

> Let's say that I organized my day such that I worked the first couple
> hours of the day on FunctionalityA, then I switched to BugB until the
> middle of the afternoon, and then I went back to FunctionalityA, such
> that at the end of the day I have completed those 2 tasks - ie my
> changesets are ready to be commited to the SVN repository.
>
> Now I would like to commit my code in such a way that it is possible
> later for somebody to quickly see and take all the changes made to
> implement FunctionalityA, and separately to correct BugB. How do I
> perform this commit action?

Commit often. You might commit this in 4 steps, depending on how
the work went. So you'd have 2 parts where the commit message
mentions work on FunctionalityA and 2 that mention BugB.

> Now you see that my problem is that the two changesets have some files
> in common, so what can I do there? I cannot select part of a file and
> commit just that part under TAG_FCT_A or TAG_BUG_B.

I don't understand how you'd do that without version control either.
But, there's
no reason to wait till the end of the day to commit - or until you
have completed
some number of changes. Commit with whatever granularity you want.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org