From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Paul Tan <pyokagan@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [RFC/GSoC] Proposal: Make git-pull and git-am builtins
Date: Tue, 24 Mar 2015 18:31:43 +0100 [thread overview]
Message-ID: <vpq4mpas3nk.fsf@anie.imag.fr> (raw)
In-Reply-To: <CACRoPnRBBVGt8PVHVEYct46abLMJvKf0+MNz7bX2nx2C7OHd3Q@mail.gmail.com> (Paul Tan's message of "Wed, 25 Mar 2015 01:22:08 +0800")
Paul Tan <pyokagan@gmail.com> writes:
> On Tue, Mar 24, 2015 at 6:19 PM, Matthieu Moy
> <Matthieu.Moy@grenoble-inp.fr> wrote:
>
>> About the timeline: I'd avoid too much parallelism. Usually, it's best
>> to try to send a first patch to the mailing list as soon as possible,
>> hence focus on one point first (I'd do that with pull, since that's the
>> one which is already started). Then, you can parallelize coding on git
>> am and the discussion on the pull patches. Whatever you plan, review and
>> polishing takes more than that ;-). The risk is to end up with an almost
>> good but not good enough to be mergeable code. That said, your timeline
>> does plan patches and review early, so I'm not too worried.
>>
>
> Well, I was thinking that after the full rewrite (2nd stage, halfway
> through the project), any optimizations made to the code will be done
> iteratively (and in separate small patches)
Yes, that's why I'm not too worried. But being able to say "this part is
done, it won't disturb me anymore" ASAP is still good IMHO, even if
"this part" is not so big.
But again, I'm thinking out loudly, feel free to ignore.
>> A general advice: if time allows, try to contribute to discussions and
>> review other than your own patches. It's nice to feel integrated in the
>> community and not "the GSoC student working alone at home" ;-).
>
> Yeah I apologize for not participating in the list so actively because
> writing the git-pull prototype and the proposal took a fair chunk of
> my time.
Don't apologize, you're doing great. I'm only pointing out things that
could be "even better", but certainly not blaming you!
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-03-24 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 16:37 [RFC/GSoC] Proposal: Make git-pull and git-am builtins Paul Tan
2015-03-24 17:22 ` Paul Tan
2015-03-24 17:31 ` Matthieu Moy [this message]
2015-03-24 18:37 ` Junio C Hamano
2015-03-25 5:55 ` Paul Tan
2015-03-25 17:54 ` Junio C Hamano
2015-03-26 5:02 ` Paul Tan
2015-03-25 9:07 ` [RFC/GSoC v2] " Paul Tan
2015-03-25 20:32 ` [RFC/GSoC] " Sebastian Schuberth
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=vpq4mpas3nk.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).