From: Ridil culous <reallyridilculous@gmail.com>
To: rsbecker@nexbridge.com
Cc: git@vger.kernel.org, reallyridilculous@gmail.com
Subject: Re: Feature Request: Allow to stash push and pop file modification times to avoid rebuilds
Date: Wed, 22 Mar 2023 12:03:09 +0100 [thread overview]
Message-ID: <20230322110309.760-1-reallyridilculous@gmail.com> (raw)
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?
next prev parent reply other threads:[~2023-03-22 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 20:46 Feature Request: Allow to stash push and pop file modification times to avoid rebuilds Ridil culous
2023-03-21 20:59 ` rsbecker
2023-03-22 11:03 ` Ridil culous [this message]
2023-03-21 21:09 ` Junio C Hamano
2023-03-22 11:13 ` Ridil culous
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230322110309.760-1-reallyridilculous@gmail.com \
--to=reallyridilculous@gmail.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).