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:03 UTC
Message-ID
<20230322110309.760-1-reallyridilculous@gmail.com>
In-Reply-To
<000a01d95c38$0acfba10$206f2e30$@nexbridge.com>
I encounter this use case many times a day and believe build consistency wouldn't be screwed for it:
- There's an existing build based on committed and uncommitted changes
- stash push the uncommitted changes
- rebase or pull
- stash pop the changes and only restore filedates for files without merges; set the current timestamp for all others
- build again

Sometimes i save and manually restore filedates from headers which are part of a precompiled header to save a quarter of an hour build time if it's not too many files. I woulnd't need this if git rebase would not refuse to rebase when there are unstaged changes like git pull does. Am i doing it wrong and there's an easier way to avoid this problem when using rebase?

Previous: rsbecker@nexbridge.comNext: Junio C Hamano
Message 3 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.