> From: Les Mikesell
> To: BRM
> Cc: "users@subversion.apache.org"
> Sent: Thursday, February 28, 2013 5:29 PM
> Subject: Re: Tagging svn:externals
>
> On Thu, Feb 28, 2013 at 3:34 PM, BRM wrote:
>
>>> No, I think the choices are to tag from the
On Thu, Feb 28, 2013 at 3:34 PM, BRM wrote:
>> No, I think the choices are to tag from the working copy or commit a
>> change after making the tag. But neither seem like the tool is
>> designed to do what I'd expect to be a common operation cleanly.
>
> What do you mean?
>
> Branching from a wor
> From: Les Mikesell
> To: BRM
> Cc: "users@subversion.apache.org"
> Sent: Wednesday, February 27, 2013 5:49 PM
> Subject: Re: Tagging svn:externals
>
> On Wed, Feb 27, 2013 at 4:44 PM, BRM wrote:
>>>
>>> Won't work - it
On Wed, Feb 27, 2013 at 4:44 PM, BRM wrote:
>>
>> Won't work - it has to be committed somewhere or it won't be built.
>
> Perhaps then you need a different tool.
> For example, git-svn[1] is might be what you want.
>
> When something is ready for QA it is pushed to a git repository for Jenkins
>
> From: Les Mikesell
> To: BRM
> Cc: "users@subversion.apache.org"
> Sent: Wednesday, February 27, 2013 5:30 PM
> Subject: Re: Tagging svn:externals
>
> On Wed, Feb 27, 2013 at 4:14 PM, BRM wrote:
>>>
>>> But that's not what I want. I
On Wed, Feb 27, 2013 at 4:14 PM, BRM wrote:
>>
>> But that's not what I want. I want the externals in tags to point to
>> previously tagged component versions. Without forcing that to be
>> committed to the trunk or encouraging copying to tags from a workspace
>> that doesn't match any trunk com
> From: Les Mikesell
> To: BRM
> Cc: "users@subversion.apache.org"
> Sent: Tuesday, February 26, 2013 6:12 PM
> Subject: Re: Tagging svn:externals
>
> On Tue, Feb 26, 2013 at 4:29 PM, BRM wrote:
>>
>>> How can a script possibly know the co
On Tue, Feb 26, 2013 at 4:29 PM, BRM wrote:
>
>> How can a script possibly know the correct tag for an external target
>> which is currently pointing at the trunk in a repository that permits
>> concurrent operations?
>
> In my example, it would simply update, then pull the revision number to
> g
> From: Les Mikesell
> To: BRM
> Cc: "users@subversion.apache.org"
> Sent: Tuesday, February 26, 2013 11:56 AM
> Subject: Re: Tagging svn:externals
>
> On Tue, Feb 26, 2013 at 8:48 AM, BRM wrote:
>>>>
>>> Agreed, but the scenario is makin
On Tue, Feb 26, 2013 at 8:48 AM, BRM wrote:
>>>
>> Agreed, but the scenario is making a QA tag from trunk work. Most of
>> these are dead ends if QA rejects them - that is, with rare exceptions
>> anything that needs to be fixed would be fixed on the trunk and a new
>> QA tag made. My thinking
> From: Les Mikesell
> To: BRM
> Cc: "users@subversion.apache.org"
> Sent: Friday, February 22, 2013 10:57 AM
> Subject: Re: Tagging svn:externals
> On Fri, Feb 22, 2013 at 9:02 AM, BRM wrote:
>>>> Not only does it solve the above, but it also enfor
On Fri, Feb 22, 2013 at 9:02 AM, BRM wrote:
>
>>> Not only does it solve the above, but it also enforces a discipline in how
>> projects are updated to use newer versions of the tags; it also requires
>> developers to be aware of which externals affect which projects - which,
>> IMHO,
>> is a g
> From: Les Mikesell
> To: BRM
> Cc: "users@subversion.apache.org"
> Sent: Thursday, February 21, 2013 11:09 AM
> Subject: Re: Tagging svn:externals
>
> On Thu, Feb 21, 2013 at 9:42 AM, BRM wrote:
>>
>>> On Wed, Feb 20, 2013 at 11:52 AM, B
On Feb 21, 2013, at 11:18, Philip Martin wrote:
> Les Mikesell writes:
>
>> Neither choice 'feels' quite right to me unless you have an
>> intermediate branch to make the change. That is, if you make it on
>> the trunk before you copy to the tag you break the likely continuing
>> work on the tr
Les Mikesell writes:
> Neither choice 'feels' quite right to me unless you have an
> intermediate branch to make the change. That is, if you make it on
> the trunk before you copy to the tag you break the likely continuing
> work on the trunk that expects the externals to also follow trunk
> com
On Thu, Feb 21, 2013 at 9:42 AM, BRM wrote:
>
>> On Wed, Feb 20, 2013 at 11:52 AM, Bob Archer wrote:
>>> Some clients like TortoiseSVN have a feature that will pin the external to
>>> the revision you are copping when doing the tag. Otherwise, you have to do
>>> it manually before or after yo
> From: Les Mikesell
> To: Bob Archer
> Cc: C M ; "users@subversion.apache.org"
>
> Sent: Wednesday, February 20, 2013 1:03 PM
> Subject: Re: Tagging svn:externals
>
> On Wed, Feb 20, 2013 at 11:52 AM, Bob Archer wrote:
>> Some clients like Tort
On Wed, Feb 20, 2013 at 12:30 PM, C M wrote:
> I am not seeing anything in: /tags/Rel_1.0.
>
> Mind you I am using the Tortoise SVN 1.7 client to do the copy.
Subversion commands don't recurse into the stuff pulled in with
externals, if that is what you are expecting. But if the thing you
tag h
I am not seeing anything in: /tags/Rel_1.0.
Mind you I am using the Tortoise SVN 1.7 client to do the copy.
On Wed, Feb 20, 2013 at 12:05 PM, Les Mikesell wrote:
> On Wed, Feb 20, 2013 at 11:58 AM, C M wrote:
> > The external definitions do specify a revision. That part is working
> fine.
> >
>
On Wed, Feb 20, 2013 at 11:58 AM, C M wrote:
> 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.
What do you mean by 'doesn't work'? The copy should have the same
externals as the sourc
On Wed, Feb 20, 2013 at 11:52 AM, Bob Archer wrote:
> Some clients like TortoiseSVN have a feature that will pin the external to
> the revision you are copping when doing the tag. Otherwise, you have to do
> it manually before or after you create your tag.
Neither choice 'feels' quite right to m
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
wrote:
> Externals are separate repositories by design. You should reference
> externals to a
@subversion.apache.org
Subject: Tagging svn:externals
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
-&
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 wrote:
> It seems that SVN does not tag svn:externals.
>
> We hav
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 chil
25 matches
Mail list logo
