Johannes Schindelin writes:
> Therefore, I would wager a bet that just the mere conversion of a
> shell script into even a primitive `run_command()`-based builtin would
> help performance on Windows in a noticeable manner.
As you correctly allege, if a patch rewrote a shell-scripted
porcelain by
Hi Paul,
On 2015-03-17 01:22, Paul Tan wrote:
> On Tue, Mar 17, 2015 at 12:49 AM, Yurii Shevtsov wrote:
>
> Generally, it would be easy to convert any shell script to C by just
> using the run_command* functions (and in less lines of code), but that
> would not be taking advantage of the potenti
On Tue, Mar 17, 2015 at 7:22 AM, Paul Tan wrote:
> Hi,
>
> On Tue, Mar 17, 2015 at 12:49 AM, Yurii Shevtsov wrote:
>> I'm going to write for this idea. As I know good proposal should
>> contain timeline and Todo estimations. What should I write in my
>> proposal, since there is no clear plan for
Hi,
On Tue, Mar 17, 2015 at 12:49 AM, Yurii Shevtsov wrote:
> I'm going to write for this idea. As I know good proposal should
> contain timeline and Todo estimations. What should I write in my
> proposal, since there is no clear plan for converting scripts to
> builtins. Thanks in advance!
I'm
Yurii Shevtsov writes:
> I'm going to write for this idea. As I know good proposal should
> contain timeline and Todo estimations. What should I write in my
> proposal, since there is no clear plan for converting scripts to
> builtins. Thanks in advance!
The fact that there is no clear plan is p
I'm going to write for this idea. As I know good proposal should
contain timeline and Todo estimations. What should I write in my
proposal, since there is no clear plan for converting scripts to
builtins. Thanks in advance!
--
To unsubscribe from this list: send the line "unsubscribe git" in
the bo
6 matches
Mail list logo
