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

[GSOC2014] History Repair Tools

From
TamerTas <tamertas@outlook.com>
Date
Mar 16, 2014, 19:09 UTC
Message-ID
<BLU0-SMTP2148A95FC508A984BDD3C50D5720@phx.gbl>
Hello everyone,

I'm Tamer Tas. I am studying computer engineering in Turkey. I'm about to complete my junior year in Middle East Technical University.

After setting up my git development environment, I've submitted patches to a microproject [1][2][3]. I'm still getting feedbacks on the microproject. Feedback cycle has been very informative.

I am interested in developing history repair tools for git. For the past days I've been learning about how git manages history, inspecting git fsck, replace, hash-object. Also I've learned how git filter-branch is used to rewrite history and the drawbacks of this approach. I've submitted the first draft of my proposal and I would love to get a feedback from Jeff King or Michael Haggarty (Mentors of the project) or the community so I can improve my proposal.

If you have any questions please feel free to ask. Thanks in advance.

Tamer Tas

[1]http://git.661346.n2.nabble.com/PATCH-GSOC2014-changed-logical-chain-in-branch-c-to-lookup-tables-tt7605343.html [2]http://git.661346.n2.nabble.com/PATCH-GSOC2014-install-branch-config-change-logical-chain-to-lookup-table-tt7605550.html [3]http://git.661346.n2.nabble.com/PATCH-GSOC2014-install-branch-config-change-logical-chain-to-lookup-table-tt7605550.html#a7605663

Message 1 of 1 in “[GSOC2014] History Repair Tools”
  1. TamerTasMar 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.