Hi There Tim,
> -----Original Message-----
> From: Tim Hill [mailto:firstname.lastname@example.org]
>  The ability to create a tag at commit time in one single
> atomic operation, via some sort of --tag switch to svn
> commit. This would certainly take care of issue (1) for me
> and would, I suspect, make
> (2b) go away for a lot of people. And, yes, I'm aware that
> this is also a tricky feature to get "right".
This feature, as it has been discussed in this thread in the past,
was to allow the user to commit their workspace to a Label/Tag without
worrying what's in HEAD, right? So you commit a copy of foo.c with changes
that you've made to make the build work, and it commits that file (along
with all the others in your workspace) to the repository, and labels them
with the label?
So.. Where does the above commit (commit my workspace to tag PRODUCTION_1_1) go,
if there are existing changes in the HEAD revision of the files you're
committing? Does it Merge them in, commit over them (and then revert them
in the next rev?), or fail completely?
Or does Subversion have to support the introduction of non-sequential changes?
(r 10 -> r 12) with r11 on the side(and not affecting/affecting HEAD?) because
that's a commit from a user's tagged workspace?
Received on Tue Nov 21 09:37:05 2006