subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From C M <cmanalys...@gmail.com>
Subject Re: Tagging svn:externals
Date Wed, 20 Feb 2013 17:58:56 GMT
The external definitions do specify a revision. That part is working fine.

I am just not clear on why a simple copy (tag) doesn't work against
externals.

On Wed, Feb 20, 2013 at 11:42 AM, Geoff Hoffman
<ghoffman@cardinalpath.com>wrote:

> Externals are separate repositories by design. You should reference
> externals to a specific revision, or tag the externals first and rewrite
> your externals to point to the tagged externals.
>
>
>
>
> On Wed, Feb 20, 2013 at 10:28 AM, C M <cmanalyst66@gmail.com> wrote:
>
>> It seems that SVN does not tag svn:externals.
>>
>> We have defined a structure such that child projects have link from a
>> parent project.
>>
>> Parent project -> child project_1
>>                       -> child project_2
>>                       -> child project_3
>>
>> However, when you go to tag a release for a child, there's nothing in the
>> /tags/Rel_X as I would normally expect.
>>
>> What's going on here?
>> Amad
>>
>
>
> Connect with us on twitter <http://twitter.com/cardinalpath>, google+<https://plus.google.com/108076800625872227241/posts>
> , facebook <http://www.facebook.com/CardinalPath>,** or linkedin<http://www.linkedin.com/company/cardinal-path>
> .
>
> Catch our next training in St Louis Feb 25 - Mar 1<http://training.cardinalpath.com/google-adwords-analytics/saint-louis/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=stlouis-2013-02-25>
> , Vancouver Mar 4 - 8<http://training.cardinalpath.com/google-adwords-analytics/vancouver/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=vancouver-2013-03-04>
> , New York City Mar 11 - 15 <http://goo.gl/y4Ojj>, Atlanta Apr 10 - 12<http://goo.gl/oJGyd>
>  or See All <http://cpath.it/Jkrs3s>.
>
> This email, including any attachments, is for the sole use of the intended
> recipient and may contain confidential information. If you are not the
> intended recipient, please immediately notify us by reply email or by
> telephone, delete this email and destroy any copies. Thank you.
>
>

Mime
View raw message