Re: Python extension commands in git - request for policy change
- From
Jeff King <peff@peff.net>
- Date
- Dec 12, 2012, 12:29 UTC
- Message-ID
- <20121212122909.GA21624@sigill.intra.peff.net>
- In-Reply-To
- <20121212122625.GB25981@thyrsus.com>
On Wed, Dec 12, 2012 at 07:26:25AM -0500, Eric S. Raymond wrote:
Show 13 quoted lines
> Jeff King <peff@peff.net>: > > I think there are really two separate use cases to consider: > > > > 1. Providing snippets of script to Git to get Turing-complete behavior > > for existing Git features. For example, selecting commits during a > > traversal (e.g., a better "log --grep"), formatting output (e.g., a > > better "log --format" or "for-each-ref --format"). > > > > 2. Writing whole new git commands in a language that is quicker or > > easier to develop in than C. > > That's good analysis. I agree with your use-case split, I guess I'm just not > very aware of the places in git where (1) is important.
Yeah, I don't think (1) is your use case at all. But when people talk about "Jeff's lua experiment", they are talking about some patches I had to do (1), which covered "log --format" (but ultimately would need more cleanup to be acceptable upstream). Maybe that clears up the discussion a little bit.
-Peff