From: Jeff King <peff@peff.net>
To: Robert David <robert.david.public@gmail.com>
Cc: Thomas Rast <trast@student.ethz.ch>,
Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: Re: GSOC idea: build in scripts and cleanups
Date: Tue, 5 Apr 2011 12:52:12 -0400 [thread overview]
Message-ID: <20110405165212.GB9965@sigill.intra.peff.net> (raw)
In-Reply-To: <201104040943.10030.robert.david.public@gmail.com>
On Mon, Apr 04, 2011 at 09:43:09AM +0200, Robert David wrote:
> Today git code consists of the base written in C and many helper shell or PERL
> scripts. While at a first time it is easier to write the script, final code is
> supposed to be in C. One of these scripts is git-add--interactive.
>
> Git-add--interactive is a helper script for git-add, which servers its options
> -i and -p. It definitely need to be integrated in git-add.
Can you expand on "definitely" here? I.e., what are the motivations for
this change? I know what some of the arguments are, and I know how _I_
would answer the question, but I want to hear what _you_ think.
And I am not just trying to be pedantic. Understanding the motivations
for a change will help us figure out the right way to go about it, and
how to figure out if we are successful at making it.
> Interfaces
> As this is mainly part of git-add, that means that it will need to be changed
> at the most.
> There are also another commands using this functionality now: git-am, git-
> checkout, git-rebase.
I don't think this is right. "am" and "rebase" have interactive modes,
but the code and functionality are not shared at all with
add--interactive. But you are missing some other commands that do have
patch modes built on add--interactive.
-Peff
next prev parent reply other threads:[~2011-04-05 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 0:41 GSOC idea: build in scripts and cleanups Robert David
2011-03-26 2:14 ` Jonathan Nieder
2011-03-26 13:39 ` Jeff King
2011-03-28 8:55 ` Robert David
2011-03-28 14:21 ` Jeff King
2011-03-30 15:39 ` Thomas Rast
2011-03-30 21:17 ` Robert David
2011-04-03 21:17 ` Robert David
2011-04-04 7:43 ` Robert David
2011-04-04 18:09 ` Junio C Hamano
2011-04-04 18:51 ` Robert David
2011-04-05 17:07 ` Jeff King
2011-04-05 18:18 ` Junio C Hamano
2011-04-05 16:52 ` Jeff King [this message]
2011-04-05 23:27 ` Robert David
2011-04-07 13:30 ` Robert David
2011-04-07 22:19 ` Junio C Hamano
2011-04-08 9:51 ` Robert David
2011-04-11 6:34 ` Jonathan Nieder
2011-04-17 18:50 ` Robert David
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=20110405165212.GB9965@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=robert.david.public@gmail.com \
--cc=trast@student.ethz.ch \
/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).