From: Corey F <coyotebush22@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: GSoC git-add--interactive improvements
Date: Wed, 04 Apr 2012 22:46:01 -0700 [thread overview]
Message-ID: <4F7D3199.5040401@gmail.com> (raw)
In-Reply-To: <CAP8UFD0V17Gag3esFd=ZDocZZoiN_4a1bjQ8rFwbBZoJEiasBA@mail.gmail.com>
On 04/04/2012 01:26 AM, Christian Couder wrote:
> Hi,
>
> On Wed, Apr 4, 2012 at 6:07 AM, Corey F<coyotebush22@gmail.com> wrote:
>> Last year's SoC ideas page included rewriting some commands in C, including
>> this one. I'm at least as comfortable with C as with Perl, but I'm guessing
>> that incorporating a rewrite into the project would be an ambitious and/or
>> dangerous idea.
> It depends how you plan to do it. In builtin/apply.c and perhaps
> elsewhere there is already some C code that is duplicated in
> git-add--interactive.perl.
> Maybe you can first make add--interactive use the C code by creating a
> helper command and then move more and more stuff from add--interactive
> to the helper command.
> Hopefully in the end the code in the helper could be used to add an
> interactive mode to git apply.
Okay, that sounds like an interesting way to approach it. The helper
command would then constitute a slightly more generic patch-chooser
interface, and most of the suggested architectural changes would be
broadly applicable.
Then again, perhaps it would be better to instead, as a sub-project,
make git-add--interactive.perl work for apply in addition to
add,commit,stash,reset. That would let me still primarily focus on
restructuring the Perl code.
I think the first few suggested design improvements, in particular, will
be valuable changes. (I often find myself wanting even more granular
control over what exact characters get staged; that may be another
improvement I'll aim for.)
I'll think about these some more and hope to put together a GSoC
application. Thanks for your insights.
Corey
prev parent reply other threads:[~2012-04-05 5:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 4:07 GSoC git-add--interactive improvements Corey F
2012-04-04 8:26 ` Christian Couder
2012-04-05 5:46 ` Corey F [this message]
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=4F7D3199.5040401@gmail.com \
--to=coyotebush22@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
/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.