git/list[1] front-page[2] threads[3] people[4] search[5] about
 

GSoC git-add--interactive improvements

From
CFCorey F <coyotebush22@gmail.com>
Date
Apr 4, 2012, 04:07 UTC
Message-ID
<4F7BC8FE.4060808@gmail.com>
Hi all,

I'd be interested in making improvements to the git add -p (etc.) interface as a Google Summer of Code project, as suggested on the ideas page [1].

The page lists some interesting ideas for both larger architectural changes and smaller interface improvements, though I agree that getting lots of community input during the project will be important. So at this point I'm wondering how much I should plan out in my proposal -- maybe pin down a few important features and a process for getting more input?

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.

Any thoughts on how best to approach this project idea are welcome.

Alternately, the "ultimate content tracking" tool to find similar sections that might have been the basis for newly added lines sounds intriguing, and I will refresh myself on the previous list discussion regarding that idea.

Thanks, Corey

1: https://github.com/peff/git/wiki/SoC-2012-Ideas
Next: Christian Couder
Message 1 of 3 in “GSoC git-add--interactive improvements”
  1. Corey FApr 4, 2012
  2. Christian CouderApr 4, 2012
  3. Corey FApr 5, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.