Hi,
On 08/29/2016 10:33 AM, Brad Jorsch (Anomie) wrote:
> On Mon, Aug 29, 2016 at 11:04 AM, John wrote:
>
>> I am running into issues where I cant set a branch on the
>> extensions/ repo for REL 1_27 and get all extensions as of that branching,
>> Instead I am forced
On Mon, Aug 29, 2016 at 11:04 AM, John wrote:
> I am running into issues where I cant set a branch on the
> extensions/ repo for REL 1_27 and get all extensions as of that branching,
> Instead I am forced to go thru one by one and manually set it, if and only
> if a
On Mon, Aug 29, 2016 at 8:34 AM John wrote:
> my thought would not only be for the bundled extensions but for
> *everything*
> under skins/ and extensions/ to get a given REL branch when a release is
> set. It might mean that some extensions get a REL for a
my thought would not only be for the bundled extensions but for *everything*
under skins/ and extensions/ to get a given REL branch when a release is
set. It might mean that some extensions get a REL for a non-compatible
branch but it would cover those extensions where devs forget to cut
branches.
On Mon, Aug 29, 2016 at 8:04 AM John wrote:
> Can we get a repo for each major release that contains core, skins, and all
> extensions in a single checkout? Right now I am updating and with all of
> the sub modules, I am running into issues where I cant set a branch on