Can Evolve be used to retire or archive an early part of

[BOGGESS Rod TENOVA INC]

Date: Mon, 16 Oct 2017 21:24:11 +0200
From: Aurélien Campéas <aurelien.campeas at pythonian.fr>
To: evolve-testers at mercurial-scm.org
Subject: Re: Can Evolve be used to retire or archive an early part of
        the history?
Message-ID: <7d394ab1-d249-fa49-4acd-283b71dcf88f at pythonian.fr>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi,



Tenova: Innovative Solutions for Metals and Mining
Visit our website at www.tenova.com
------------------------------------------------------------------
Confidentiality Notice : This message, together with its attachments, contains strictly confidential information and is intended only for the addressee identified above,who is the sole party authorized to use
 and copy it and, assuming any related liability , to forward it to others. Anyone receiving this message by mistake or reading it without authorization is hereby notified that storage, reproduction, disclosure or distribution of the message to persons other than the addressee is strictly forbidden. They are asked to return the message immediately to the sender and to erase the original message received.
Thank you.

Le 16/10/2017 à 17:45, BOGGESS Rod   TENOVA INC a écrit :
> We have a baseline copy of our code that is cloned at the start of
> each project. Modifications typically involve customizations for a
> given customer, but a few enhancements and bug-fixes go through a
> review process and are incorporated back into the baseline. As a
> result, our baseline grows ever longer. So fare, we’re not in any
> danger of the number of revisions creating a problem, but the
> likelihood of ever doing a daggy change is as close to zero as to be unworthy of distinction.
> There is only the historical value for reference that need only be
> maintained on the server, with no need to carry that history to each
> developer’s and each customer’s cloned repo. I don’t see an obvious
> way to mark a part of past history for reference-only though. Marking
> the past history as obsolete doesn’t seem to work for this case. I was
> wondering if there were a mechanism that would allow this.

Not sure if I understand you well but ... you can keep fixing your baseline/boostrap chunk of history in its own repo, and when creating a new repo for customization, you just clone that history and *fold* all its changesets into just one, initial "baseline commit".

Regards,
Aurélien.


                        :-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:

I was hoping to keep the link between the baseline and the clone to facilitate implementation of patches that do go backwards. Starting from a new repo would break that link.

I thought there was a problem with speed when the repo grows too large, and that Facebook was doing something to limit the amount of the repo that the system downloaded locally. I guess I assumed that this was being implemented in mercurial, but perhaps they've forked it and modified the code for custom usage.

It's unpleasant, but I can always start a new repo for the baseline, but the history wouldn't be a link, you'd have to go searching through two (or in time, more) repos to perform a thorough search of the history(ies). I was hoping that you could mark a part of the past history as obsolete and leave a link to an archived version of the full history. Thanks anyway.