On 4 November 2011 22:14, Felix Saphir <felix.saphir_at_kantarmedia.com> wrote:
> Am 04.11.2011 16:05, schrieb Lucien Roten:
>>> Am 04.11.2011 15:42, schrieb Lucien Roten:
>>>>> Am 04.11.2011 12:58, schrieb Lucien Roten:
> [check several externals for updates at once]
>>>>> Why not just initiate an update?
>>>> Because my external propertie is a tag for having a stable
>>>> version of my other project.
>>> And you reference a tag in the property, because you want to use a
>>> stable version, right? Why do you need an easy way to check for a
>>> newer version then? Tags are not supposed to change, and if there's
>>> a new release, you'd have to review it anyway.
>> Yes that's right. My goal is to know if the project update to the
>> next stable version (new Tag) and choose if I update my external
>> property or not.
>> The only way to know that is manual control ? Lucien
> I still don't think that there's a need for an easier way to check for
> updates of your externals. That might make sense, if you were working
> with their HEAD revision. But then you could just do a regular update.
> How often do you expect stable releases? Since it's going to be a new
> tag, checking the externals doesn't help anyway.
Either use the commit monitor to check for new commits to the tags
directory (check once a day, once a week?) or get the external repo
set up with a post-commit hook to send you an email when a new tag is
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-05 01:00:47 CET