All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Todd Zullinger <tmz@pobox.com>,
	git@jeffhostetler.com, git@vger.kernel.org, gitster@pobox.com,
	Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH v7 2/2] json-writer: t0019: add Python unit test
Date: Wed, 6 Jun 2018 22:49:13 -0400	[thread overview]
Message-ID: <20180607024913.GA9351@sigill.intra.peff.net> (raw)
In-Reply-To: <20180607022353.GA3898@sigill.intra.peff.net>

On Wed, Jun 06, 2018 at 10:23:53PM -0400, Jeff King wrote:

> Though maybe I am wrong that the remote-svn stuff requires python. I
> thought it did, but poking around, it looks like it's all C, and just
> the "svnrdump_sim" helper is python.

I think I was getting this mixed up with the git_remote_helpers python
work, which was removed long ago in ae34ac126f (git_remote_helpers:
remove little used Python library, 2013-09-07).

Note that it really changes much, but I was curious enough to dig down.

-Peff

  reply	other threads:[~2018-06-07  2:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 16:33 [PATCH v7 0/2] json-writer V7 git
2018-06-05 16:33 ` [PATCH v7 1/2] json_writer: new routines to create data in JSON format git
2018-06-05 16:33 ` [PATCH v7 2/2] json-writer: t0019: add Python unit test git
2018-06-06 17:10   ` Todd Zullinger
2018-06-06 21:03     ` Jeff King
2018-06-06 21:11       ` Jeff Hostetler
2018-06-07  0:16       ` Ramsay Jones
2018-06-07  1:49         ` Todd Zullinger
2018-06-07  2:38           ` Jeff King
2018-06-07  2:23         ` Jeff King
2018-06-07  2:49           ` Jeff King [this message]
2018-06-07 19:03           ` Ramsay Jones
2018-06-06 21:05     ` Jeff Hostetler

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=20180607024913.GA9351@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@jeffhostetler.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jeffhost@microsoft.com \
    --cc=ramsay@ramsayjones.plus.com \
    --cc=tmz@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.