Hi Sergio,

Sergio Callegari wrote:

>           Initially, I thought that the archimport was something
> that needed git to be recompiled, while now I see that it is a
> script that I can simply drop somewhere and make accessible by git
> via an environment variable.
>
> For tla, my hope is that the tla deb from debian stretch or ubuntu
> xenial, zesty or artful can remain installable for a long time in
> future distros, since its dependencies seem to be rather minimal.
[...]
> Jonathan Nieder wrote:

>> If you would use it to recover tla data from backups,
>> why not convert that tla data to git format today
>
> Because backup contain very obsolete stuff, are messed and are used
> "lazily". Only when something requires the history of some old stuff
> to be checked to understand its genesis, and there is no git repo,
> one gets the courage to seek and extract the corresponding tla
> archive from the backup and convert it to git. Which is the reason
> why I have this stuff around so many years after something way
> better than tla came around.  Unfortunately, I understand that
> laziness is not a very nice explanation.

That makes sense.  I am going to try to move git-archimport.perl to
contrib/ upstream and package it in either /usr/share/doc/git/contrib/
or /usr/share/git-core/contrib/ like other contrib scripts.

I'll include instructions in /usr/share/doc/git/README.Debian for
using it.

Thanks for the patient explanations.

Sincerely,
Jonathan

Reply via email to