Thread (1 message) 1 message, 1 author, 2016-06-15
  • (off-list ancestor, not in this archive)
  • Re: deprecating more · Horst von Brand <hidden> · 2016-06-15

Re: deprecating more

From: Horst von Brand <hidden>
Date: 2016-06-15 22:42:06

Junio C Hamano [off-list ref] wrote:

[About axing programs]
Among them, I could be talked into keeping git-export on the
condition that we will add a counterpart git-import that can
read git-export output and recreate an identical repository
[*1*]; without something like that, I doubt its usefulness,
especially since "git-whatchanged" is far more useful for
everyday use.

[Footnote]

*1* which I think actually is impossible without fixing
git-export first so that it exports the initial commit.  I may
be mistaken.
Given that you can just tar the whole repository up and handle it that way,
all that work makes little sense.

Note that bk export (and cg-export) copy the current snapshot into a
directory or tarball, so this doesn't do what I'd expected.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help