Lars Schneider writes:
> Please note that I've recently refactored the capabilities negotiation a bit:
> https://github.com/git/git/commit/1514c8edd62d96006cd1de31e906ed5798dd4681
>
> This change is still cooking in `next`. I am not sure how this should/could
> be handled but maybe you can use my
> On 24 Jul 2017, at 23:38, Jonathan Tan wrote:
>
> Refactor, into a common function, the version and capability negotiation
> done when invoking a long-running process as a clean or smudge filter.
> This will be useful for other Git code that needs to interact similarly
> with a long-running pr
On Tue, 25 Jul 2017 10:38:51 -0400
Ben Peart wrote:
> Christian Couder has been working on a similar refactoring for the perl
> versions of very similar helper functions. They can be found in the
> following patch series:
>
> https://public-inbox.org/git/20170620075523.26961-1-chrisc...@tuxfa
On 7/24/2017 5:38 PM, Jonathan Tan wrote:
Refactor, into a common function, the version and capability negotiation
done when invoking a long-running process as a clean or smudge filter.
This will be useful for other Git code that needs to interact similarly
with a long-running process.
Chris
Hi,
Jonathan Tan wrote:
> Refactor, into a common function, the version and capability negotiation
> done when invoking a long-running process as a clean or smudge filter.
> This will be useful for other Git code that needs to interact similarly
> with a long-running process.
>
> Signed-off-by: J
Refactor, into a common function, the version and capability negotiation
done when invoking a long-running process as a clean or smudge filter.
This will be useful for other Git code that needs to interact similarly
with a long-running process.
Signed-off-by: Jonathan Tan
---
This will be useful
6 matches
Mail list logo
