[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Commit warning about a tag

From: Kristoffer Lunden <kristoffer.lunden_at_comeon.com>
Date: Wed, 28 Aug 2013 10:57:15 +0200

Hi!

This is meant to continue this thread with the same name:
https://groups.google.com/forum/#!searchin/tortoisesvn-dev/commit$20to$20tag/tortoisesvn-dev/Bp_M7FK4BE0/vZxECV6Kb5cJ
- but I don't know how to reply there, if possible at all.

Anyhow. The thing is that Tortoise warns/complains on every commit
that it might be a tag commited to, when there's a *.tag file
involved. This does not make sense, since a tag would be a directory.

The last words in the discussion was:

>> Is it not enough to check that directory name does not contain 'tag'.
>> Otherwise anyone who uses .tag files is going to hit this on every
>> commit.
>
> Settings->Revision Graph->Classification Patterns
> if you remove the trunk/branches/tags strings there, the check will be
> skipped.
>
> And it really only checks for /tags/, not for .tags or something else.

And this is not correct, it does warn on 'tag' without the 's' and
changing the setting does not help. So this check is probably done
somewhere else.

Not a big issue, but for a big Java/JSP project with tons of tag files
(and many small commits) it gets pretty annoying quickly. Just wanted
to let you know this is a different issue from the 'tags' setting.

Proposed solution, only check for 'tags' and/or that it's a directory. :)

Thanks,

/ Kristoffer

-- 
________________________________
Kristoffer Lundén
SOFTWARE DEVELOPER
+46 700 902802
kristoffer.lunden_at_comeon.com
www.comeon.com
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3063453
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-28 11:38:18 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.