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

Re: Delete local TAGS files after Update?

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 15 Apr 2011 09:28:29 -0400

On Fri, Apr 15, 2011 at 09:09, Doug Ivison <DougsEmail4Dev_at_aol.com> wrote:
> Hi, and thanks for all the thought and creativity put into TortoiseSVN.
> I'm a new user of both SVN, and TortoiseSVN.
> During my first UPDATE after creating tags, TortoiseSVN appears to have downloaded all the files in the entire project, to multiple tags folders.
> 1) First, my question:  can I delete the contents of the *local* tags folder, without affecting the repository?

You can (Windows Delete, not SVN Delete), but they'll be back the next
time you run SVN Update.

It sounds like you checked out your whole repository or project. Only
check out the level you actually need to work on (trunk or a branch).
Or you can do a Sparse Checkout & only retrieve the areas you need.

> 2) Enhancement suggestion:  update prompting.
> It would be wonderfully helpful if the UPDATE function had a dialog like the COMMIT function, showing which files were about to be downloaded by update, allowing them to be checked-or-unchecked for updating, and allowing a double-click a filename, like in the "check for modifications" function, to bring up a differences function.
> ((This would also address the wishes in this message:
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=692589&orderBy=createDate&orderType=desc ))

The wishes in that post are 5 years old and addressed by my comment above.

> The reason I do not see this as redundant (already done in "check for modifications") is because the check for mods does not list these tags files... check for mods showed less than 10 files, then update downloaded over 7000.  I suppose another way to approach (2) would be to enhance check for mods to show all files that would be affected/downloaded by the update command.

This would require some extra server round-trips, and immediately
after polling the server the data would be stale; someone could commit
a second later and you wouldn't know it.

> 3) Lesser/easier enhancement suggestion:  information.
> ((This could also help with the wishes in this msg:
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2670999&orderBy=createDate&orderType=desc ))
> It would be great if the update action gave more information, such as which revision the file being updated is from.

That isn't known definitively by Subversion until the end of the
update. You can poll the server and make a guess, but until the actual
update completes successfully, it remains only a guess.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-04-15 15:29:19 CEST

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