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

[GSoC 2014] Refactoring git rebase --interactive

From
Quint Guvernator <quintus.public@gmail.com>
Date
Mar 16, 2014, 20:13 UTC
Message-ID
<CALs4jVE16V41z6X7dg-kyYeRi0b=mZZ=iSN_sOUmcZREezN_ew@mail.gmail.com>
Hi again, Git community!

My name is Quint Guvernator, and I am participating in the Google Summer of Code program. I am in university at the College of William and Mary in Williamsburg, VA and plan to major in Computer Science and Linguistics.

I have been working on a microproject [1][2] to get the hang of submitting patches and working with the mailing list.

I have just submitted my proposal for git rebase --interactive through the google-melange website. In brief, I plan to refactor the shell script, cleaning up parts where the code is incohesive or difficult to decipher; add functionality to the script; and improve documentation by describing the script in comments and improving our user docs. I think it is important not to rush into new features, however, and detail in my proposal the extent to which I will stay in contact with the community through this list and on IRC.

Should the work on rebase --interactive not take all summer, I would work to improve the quality of Git documentation. I am a native English speaker and copy-edit a local newspaper, so I feel I am qualified to edit and extend the Git documentation.

I am happy to receive private mail, so please send any issues or questions you may have either to the list or directly to my inbox.

Thanks for your consideration for GSoC.
--Quint

[1]: http://thread.gmane.org/gmane.comp.version-control.git/243940 [2]: http://thread.gmane.org/gmane.comp.version-control.git/244159

Message 1 of 1 in “[GSoC 2014] Refactoring git rebase --interactive”
  1. Quint GuvernatorMar 16, 2014

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.