From: "Stephen Robin" <stephen.robin@gmail.com>
To: "'Paul Tan'" <pyokagan@gmail.com>, <git@vger.kernel.org>
Cc: "'Johannes Schindelin'" <johannes.schindelin@gmx.de>,
"'Duy Nguyen'" <pclouds@gmail.com>
Subject: RE: [PATCH/RFC/GSOC] make git-pull a builtin
Date: Wed, 18 Mar 2015 08:38:09 -0000 [thread overview]
Message-ID: <000701d06156$dd3145e0$9793d1a0$@gmail.com> (raw)
In-Reply-To: <1426600662-32276-1-git-send-email-pyokagan@gmail.com>
> Paul Tan writes:
> I would like to share this very rough prototype with everyone.
...
> I started this as a just-for-fun exercise to learn about the git internal
API
I started to rewrite git-pull for similar reasons a couple of months ago,
but I haven't had time to complete it. It looks like my version has less
work remaining than yours, would you like me to share it?
> Finally, there is the possibility that in the process of conversion bugs
or incompatible behavioral changes may be introduced which are not caught by
the test suite. Ideally, I think the solution is to improve the test suite
and make it as comprehensive as possible, but writing a comprehensive test
suite may be too time consuming.
This is why I haven't had time to finish and submit my patch. While the c
code is pretty much complete, I felt the test suite needed some extension
before I could be confident the new code is correct.
next prev parent reply other threads:[~2015-03-18 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 13:57 [PATCH/RFC/GSOC] make git-pull a builtin Paul Tan
2015-03-18 8:38 ` Stephen Robin [this message]
2015-03-18 9:24 ` Johannes Schindelin
2015-03-18 9:00 ` Johannes Schindelin
2015-03-21 14:00 ` Paul Tan
2015-03-21 17:27 ` Johannes Schindelin
2015-03-18 17:52 ` Matthieu Moy
2015-03-21 13:23 ` Paul Tan
2015-03-21 17:35 ` Johannes Schindelin
2015-03-22 17:39 ` Paul Tan
2015-03-23 9:07 ` Johannes Schindelin
2015-03-23 10:18 ` Duy Nguyen
2015-03-24 15:58 ` Paul Tan
2015-03-18 22:26 ` Junio C Hamano
2015-03-21 13:40 ` Paul Tan
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='000701d06156$dd3145e0$9793d1a0$@gmail.com' \
--to=stephen.robin@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=pclouds@gmail.com \
--cc=pyokagan@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 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.