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

Re: integrating make and git

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Apr 15, 2009, 21:01 UTC
Message-ID
<alpine.LNX.1.00.0904151654330.10753@iabervon.org>
In-Reply-To
<3a69fa7c0904150947w25783199n6e304d7b4efcd051@mail.gmail.com>
On Wed, 15 Apr 2009, E R wrote:
Show 6 quoted lines
> Ok - I was wrong about the timestamps not getting updated. Thanks for
> that correction.
> 
> However, what about the idea of associating the result of a build with
> the hash of the source files used by the build, and using git to
> compute the hash?

It's a reasonable idea, in general, but may or may not be useful for any particular problem. In general, the objects in your subdirectories are also doing to depend on some but not most things from an include directory, and so there's not much benefit you can get on a per-directory granularity. On the other hand, I've gotten good results by embedding the commit sha1 in generated object files, which allowed me to exactly identify different builds much later, and even figure out what the source that went into them was.

	-Daniel
*This .sig left intentionally blank*
Previous: Nguyen Thai Ngoc DuyNext: John Bito
Message 9 of 14 in “integrating make and git”
  1. E RApr 15, 2009
  2. Matthieu MoyApr 15, 2009
  3. Daniel BarkalowApr 15, 2009
  4. E RApr 15, 2009
  5. Robin RosenbergApr 15, 2009
  6. Jeff KingApr 16, 2009
  7. Matthieu MoyApr 16, 2009
  8. Nguyen Thai Ngoc DuyApr 16, 2009
  9. Daniel BarkalowApr 15, 2009
  10. John BitoApr 15, 2009
  11. Ben JacksonApr 16, 2009
  12. David KågedalApr 16, 2009
  13. Dmitry PotapovApr 17, 2009
  14. Ealdwulf WuffingaApr 18, 2009

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.