From: Felipe Contreras <felipe.contreras@gmail.com>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] git_remote_helpers: remove little used Python library
Date: Sat, 7 Sep 2013 20:10:07 -0500 [thread overview]
Message-ID: <CAMP44s1cUdy8rOU7GUAbFfdMsM7+=_DEDSXGh8hK1CT+0E53qg@mail.gmail.com> (raw)
In-Reply-To: <23afa908bb2e21779ea96da8c149dcc43aa72eda.1378570768.git.john@keeping.me.uk>
On Sat, Sep 7, 2013 at 11:19 AM, John Keeping <john@keeping.me.uk> wrote:
> When it was originally added, the git_remote_helpers library was used as
> part of the tests of the remote-helper interface, but since commit
> fc407f9 (Add new simplified git-remote-testgit, 2012-11-28) a simple
> shell script is used for this.
>
> A search on Ohloh [1] indicates that this library isn't used by any
> external projects and even the Python remote helpers in contrib/ don't
> use this library, so it is only used by its own test suite.
>
> Since this is the only Python library in Git, removing it will make
> packaging easier as the Python scripts only need to be installed for one
> version of Python, whereas the library should be installed for all
> available versions.
For the record, there was a user of this:
https://github.com/msysgit/git/tree/v1.8.1.msysgit.1/git_remote_helpers
However, in the latest msysgit master it seems the git-remote-hg
helper is gone, I don't know if by mistake or what. Johannes
Schindelin made many claims about it being more complete and what not,
but who knows what actually happened.
--
Felipe Contreras
prev parent reply other threads:[~2013-09-08 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 16:19 [PATCH] git_remote_helpers: remove little used Python library John Keeping
2013-09-07 20:14 ` Sverre Rabbelier
2013-09-08 1:10 ` Felipe Contreras [this message]
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='CAMP44s1cUdy8rOU7GUAbFfdMsM7+=_DEDSXGh8hK1CT+0E53qg@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
--cc=srabbelier@gmail.com \
/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).