From: Robert David <robert.david.public@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Thomas Rast <trast@student.ethz.ch>,
Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: Re: GSOC idea: build in scripts and cleanups
Date: Mon, 28 Mar 2011 10:55:22 +0200 [thread overview]
Message-ID: <201103281055.23578.robert.david.public@gmail.com> (raw)
In-Reply-To: <20110326133939.GB2859@sigill.intra.peff.net>
[-- Attachment #1: Type: Text/Plain, Size: 2003 bytes --]
Dne sobota 26 března 2011 14:39:39 Jeff King napsal(a):
> On Fri, Mar 25, 2011 at 09:14:35PM -0500, Jonathan Nieder wrote:
> > > I was also thinking if there isn't PERL a better choice in rewriting
> > > shell scripts, due to planed porting (android, etc). Better than C.
> > > But I don't know android and other platform so much, so thats why I'm
> > > asking.
> >
> > So far (on Windows and various Unixen) it seems that C is much easier
> > to work with as far as porting goes.[2]
>
> If I were considering cleaning up and porting add--interactive to C, I
> think I would probably start with just porting the "-p" patch loop
> first. I think it's the part that most people use, and most callers
> don't support a generic "-i" but just the "-p" interface (e.g., you can
> do "git add -i" or "git add -p", but only "git checkout -p"). And that
> cuts down the size of the task somewhat.
I have read all the code in git-add--interactive. If I understand that
correct, you mean to separate -i and -p int two different commands.
And make the -p option more like the -i (but just only for patching).
And consequently port them to C.
>
> As far as cleanup versus features, I think Thomas would have to comment
> on that. He is the one who did the most work on patch-mode, and
> therefore the one who most thinks it needs cleaned up. :)
>
Is Thomas going to be a mentor in this task?
Robert David.
> > [1] Android is an odd example because the platform uses Java heavily
> > (so JGit might be a better fit for it). Perhaps the wish for android
> > support should have been put on the Eclipse ideas page[2] and a link
> > added to git's; I dunno.
>
> Yeah, I'm not sure what an Android port would quite look like. In theory
> I could probably build stock git for my rooted N1 using a
> cross-compiler. But I can't imagine what I would use it for. A native
> app seems like it would be more useful, and that pretty much requires
> Java.
>
> -Peff
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-03-28 8:55 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 [this message]
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
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=201103281055.23578.robert.david.public@gmail.com \
--to=robert.david.public@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--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 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.