Felipe Contreras <felipe.contre...@gmail.com> wrote:
> Eric Wong wrote:
> > Felipe Contreras <felipe.contre...@gmail.com> wrote:
> > > No updates since 2010, and no tests.
> > Who benefits from this removal? Is this causing a maintenance
> > burden for Junio?
> It is cruft that nobody uses and we are not even testing.
We do not know nobody uses it. I have old GNU Arch projects I have not
looked at in a decade. There is a small chance I may use archimport
again (whether for nostalgia or contractual/legal reasons).
Of course I know to extract archimport from history, but someone in
the future may not know the existence of it.
> > > Plus, foreign SCM tools should live out-of-tree anyway.
> > Even if so, there ought to be a transitionary period in case there are
> > any users. We would need to warn potential users of its impending
> > removal in the documentation and at runtime.
> All right, so you are OK with adding deprecation warnings whenever the
> tool is run, and a note in the documentation?
No, I am not convinced existing foreign SCM tools should move
out-of-tree. Perhaps something like the following would be helpful:
Warning: Like GNU Arch, git-archimport is unmaintained. Please
contact us at email@example.com in case you run into problems,
want to help, or just want to tell us it still works.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html