RE: Re: File externals & feature requests

> "As you mention there already: the check-for-modifications dialog provides that feature very well."

Stefan, thats not what im saying at all, i was saying that at best the check-for-modifications dialog (CFMD) provides a crude way to see if a link is an external, but if the external is "up-to-date" you will never know that it is even there in the wc.

> "Items which are not relevant for a commit are of course not shown - but then why would you need the external information there anyway?"

well in your message/post # "2375993" in reference to post # "2374494" you said
> "I think it's much much better to manually tag the externals."

Im just saying in a large project/wc its pretty hard to manually tag the external if you dont know that the files/folders are externals. If one wants to tag/branch and wants to pin down the externals (even manually) there is no way for that person to know a particular folder is an external (if its up-to-date[UTD]) and hence thats why this info would be useful.

As you mentioned the only current way to know about the presence of externals in a project is if the wc external files have changes (via CFMD), but again if they are "up-to_date" (UTD) they are likely to be overlooked when people are trying to go through their design and lock the externals to a revision manually. Which bring us back to a more automated approach to search the wc for externals (both up to date and modified) as in part 3 of post # 2374494

I understand that the full-automation method might be "too much", but think that if there was a way simply to identify ALL externals (UTD and modified) in a wc then it would make any user initiated tag operations easier when externals are involved.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2376056

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-07-27 18:54:38 CEST