On 12/2/06, Les Mikesell <lesmikesell@gmail.com> wrote:
> > If you were using a hook script that disallowed putting something in
> > the tag directory as anything other than a copy, would that satisfy
> > your requirements?
>
> Yes, although I really only want to keep it from happening by
> accident. Is there a handy way to verify after the fact that
> the tag only contains revisions committed elsewhere? Or can
> the hook script take an option to force an override?
I'll look at writing such a hook script as time permits, then. I will
probably try the approach of looking at the type of modification, or
else the verbose log message as described below.
I don't think you can get parameters to the hook script without doing
something dirty, like parsing log messages.
Regarding being able to verify the branch: happily, running a verbose
log appears to catch files that aren't committed but are copied.
Invoking this from the check-out of a tag made from an uncommitted WC:
[bob@localhost t0]$ svn log -v . --stop-on-copy
------------------------------------------------------------------------
r22 | bob | 2006-12-04 13:43:34 -0600 (Mon, 04 Dec 2006) | 2 lines
Changed paths:
A /dmitri/tags/t0 (from /dmitri/trunk:15)
M /dmitri/tags/t0/hello.txt
A /dmitri/tags/t0/newdir/newfiles
A /dmitri/tags/t0/static.txt (from /dmitri/trunk/static.txt:21)
Note that the files that were checked in are explicitly shown as
copies with specific revision numbers. hello.txt was an existing file
with uncommitted modifications at time of copy. newfiles is an added,
but uncommitted, file at time copy.
So, to answer your question, it appears that you can easily check for
uncommitted files in a tag.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 4 20:53:08 2006