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

Re: Feature Request: Allow to stash push and pop file modification times to avoid rebuilds

From
RCRidil culous <reallyridilculous@gmail.com>
Date
Mar 22, 2023, 11:13 UTC
Message-ID
<20230322111329.781-1-reallyridilculous@gmail.com>
In-Reply-To
<xmqq5yathkwh.fsf@gitster.g>
Sorry, i wrongly addressed my reply before (https://lore.kernel.org/git/20230322110309.760-1-reallyridilculous@gmail.com/) to rsbecker.
Junio C Hamano <gitster@pobox.com> wrote:
Show 6 quoted lines
> Now what timestamp should "stash pop" give to the working tree files
> in this case?  The contents of the file probably is identical to the
> timestamp of the working tree files immediately before "stash push"
> was run.  If we restore the original timestamp, because it is way
> older than the build artifacts of your second build (which was done
> after "stash push"), the build artifacts would not be recreated.
The usecase for which i'd like to have the feature would avoid that because there would be only build artefacts from the time of "stash push".
Previous: Junio C Hamano
Message 5 of 5 in “Feature Request: Allow to stash push and pop file modification times to avoid rebuilds”
  1. Ridil culousMar 21, 2023
  2. rsbecker@nexbridge.comMar 21, 2023
  3. Ridil culousMar 22, 2023
  4. Junio C HamanoMar 21, 2023
  5. Ridil culousMar 22, 2023

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.