Create a new repository starting with tip?

[Igor Lautar]

On Thu, Feb 18, 2010 at 3:15 PM, greg fenton <greg.fenton at gmail.com> wrote:
> On Thu, Feb 18, 2010 at 02:51, Igor Lautar <igor.lautar at gmail.com> wrote:
>>
>> Why not create a new repo that is shared (from this point on), but
>> keep old one as read-only for internal reference?
>>
>
> The big pushback by the internal developers is the inefficiency of
> doing historical diffs between the current revision on the new
> (external) repository and the historical revisions of the same files
> on the internal repository.
>
> These are extremely productive developers.  Cutting into that
> productivity is something I'd like very much to avoid.  Thus the
> search for this type of solution.

Well, you will end up with inneficiency either way, as you have to
manually merge new changes to "external only" repo.
But I imagine this would be relativelly easy to automate, as Giergos
explained before.

I do not know the specifics why history is needed, but my experience
is that this stuff is made to look more trouble than it is by the
developers because its a change from their workflow (have experienced
few such changes, so I talk from my own experience). Once they adapt,
everything is back to normal.

Regards,
Igor