From: Felipe Contreras <felipe.contreras@gmail.com>
To: Eric Wong <normalperson@yhbt.net>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Martin Langhoff <martin@laptop.org>
Subject: Re: [PATCH v1 1/2] Remove 'git archimport'
Date: Fri, 09 May 2014 04:20:40 -0500 [thread overview]
Message-ID: <536c9de8f07ae_39ea14ab310f9@nysa.notmuch> (raw)
In-Reply-To: <20140509085937.GA29347@dcvr.yhbt.net>
Eric Wong wrote:
> Felipe Contreras <felipe.contreras@gmail.com> wrote:
> > As a minimal token that anybody might possibly be using it, I would like
> > to see it work at least once. Since you said you have arch repos, can
> > you confirm that it does something?
>
> Those repos are in offline/offsite storage and I do not have time to
> retrieve them.
Then we have no reason to believe they still work, and therefore, no
reason to believe anybody is using this.
> I've forgotten how to use tla to get a public repo, even.
No surprises there given how unfriendly tla is.
> > Eric Wong wrote:
> > > No, I am not convinced existing foreign SCM tools should move
> > > out-of-tree. Perhaps something like the following would be helpful:
> >
> > Tell that to Junio.
> >
> > If tools like git-remote-hg with tests and active maintanance and many
> > users cannot be in the core, why should 'git archimport' be?
>
> Perhaps it's easier to deal with a benign, unmaintained tool than
> to deal with you as a maintainer?
That is irrelevant to the bad quality of 'git archimport'.
> > Would you at least be OK with a demotion to contrib/?
>
> I don't see the point of moving it around, even.
So basically you think we should keep 'git archimport' forever in the
core, even if nobody uses it ever. So much for compromises.
I think it should be removed altogether. If somebody complains the were
using the tool, it can be added to contrib/ as a temporary measure.
--
Felipe Contreras
next prev parent reply other threads:[~2014-05-09 9:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 1:33 [PATCH v1 0/2] Remove foreign SCMs Felipe Contreras
2014-05-09 1:33 ` [PATCH v1 1/2] Remove 'git archimport' Felipe Contreras
2014-05-09 5:50 ` Eric Wong
2014-05-09 7:11 ` Felipe Contreras
2014-05-09 8:15 ` Eric Wong
2014-05-09 8:36 ` Felipe Contreras
2014-05-09 8:59 ` Eric Wong
2014-05-09 9:20 ` Felipe Contreras [this message]
2014-05-09 14:54 ` Jeff King
2014-05-09 15:15 ` Felipe Contreras
2014-05-09 16:33 ` Felipe Contreras
2014-05-09 17:44 ` Junio C Hamano
2014-05-09 17:52 ` Felipe Contreras
2014-05-09 18:33 ` Thomas Adam
2014-05-09 19:21 ` Eric Wong
2014-05-09 22:01 ` Felipe Contreras
2014-05-13 18:16 ` Martin Langhoff
2014-05-13 18:01 ` Martin Langhoff
2014-05-13 18:05 ` Felipe Contreras
2014-05-13 18:17 ` Martin Langhoff
2014-05-13 18:25 ` Felipe Contreras
2014-05-13 18:19 ` Junio C Hamano
2014-05-09 1:33 ` [PATCH v1 2/2] Remove 'git quiltimport' Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=536c9de8f07ae_39ea14ab310f9@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin@laptop.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).