On Sat, Dec 15, 2012 at 10:06 AM, Daniel Shahaf wrote:
> Stefan Scherer wrote on Wed, Dec 12, 2012 at 14:13:01 -0500:
>> Hello again,
>>
>> I just noticed my previous email got somewhat scrambled.
>>
>> The idea was to have notation like the following
>>
>> ../../common/module1@RELATIVE module1
>>
Stefan Scherer wrote on Wed, Dec 12, 2012 at 14:13:01 -0500:
> Hello again,
>
> I just noticed my previous email got somewhat scrambled.
>
> The idea was to have notation like the following
>
> ../../common/module1@RELATIVE module1
>
> in order to peg an external to the revision of the folder o
On Wed, Dec 12, 2012 at 02:13:01PM -0500, Stefan Scherer wrote:
> The idea being that we simply move the peg revision on a plugin in order to
> include the latest QA approved plugin in a release candidate build.
> After QA approved the candidate we simply tag the staging branch as a
> release.
>
>
Hello again,
I just noticed my previous email got somewhat scrambled.
The idea was to have notation like the following
../../common/module1@RELATIVE module1
in order to peg an external to the revision of the folder owning the the
external property.
The reason why I would like such a feature is
Stefan Scherer wrote on Mon, Dec 10, 2012 at 16:09:47 -0500:
> I would like to be able to peg in product to a particular revision and
> have and
> be of that same revision without having to maintain the peg
> at trunk/plugin/p1/EXTERNALS which would have to
> be constantly moving.
>
>
> http:/
Hi,
I am wondering if it is possible to have a relative path external
have a revision that stays with the revision of the folder that has the
external property.
The idea is that I have a structure as follows:
trunk/common/module1
trunk/common/module2
trunk/plugin/p1/EXTERNALS/
trunk/plugin/p1
