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

Re: Is there any efficient way to track history of a piece of code?

From
DLDavid Lang <david@lang.hm>
Date
May 9, 2014, 06:56 UTC
Message-ID
<alpine.DEB.2.02.1405082354100.17457@nftneq.ynat.uz>
In-Reply-To
<CAHz2CGV6==abb0SrXOyqwumxEVLFnTtqe1Z4j2A7XcvJNuoAHw@mail.gmail.com>
On Thu, 8 May 2014, Jianyu Zhan wrote:
> That being said, storing abstract syntax tree, instead of raw object in git.
> But that goes too far...

well, there are the clean/smudge filters, you can have it run everything through a prettyprinter as it's checked in.

with a little effort, you could do something along the lines of git filterbranch that could create a clone of a repo with all commits cleaned up.

David Lang
Previous: Junio C HamanoNext: David Kastrup
Message 5 of 7 in “Is there any efficient way to track history of a piece of code?”
  1. Jianyu ZhanMay 8, 2014
  2. Jeff KingMay 8, 2014
  3. Jianyu ZhanMay 8, 2014
  4. Junio C HamanoMay 8, 2014
  5. David LangMay 9, 2014
  6. David KastrupMay 8, 2014
  7. Chris PackhamMay 8, 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.