From: <rsbecker@nexbridge.com>
To: "'Ridil culous'" <reallyridilculous@gmail.com>, <git@vger.kernel.org>
Subject: RE: Feature Request: Allow to stash push and pop file modification times to avoid rebuilds
Date: Tue, 21 Mar 2023 16:59:28 -0400 [thread overview]
Message-ID: <000a01d95c38$0acfba10$206f2e30$@nexbridge.com> (raw)
In-Reply-To: <CAEg4PiL+Y8yxCpWaQFUswTj1qegT084w9m0rc14Kf1dEWk5G-g@mail.gmail.com>
On Tuesday, March 21, 2023 4:47 PM, Ridil culous wrote:
>"git stash push"
>later followed by
>"git stash pop"
>does restore files but doesn't restore file modification times.
>
>It would be great if there would be an option to opt in for stashing and restoring the
>file modification times because not restoring them potentially triggers rebuilds for
>many IDEs (MSVC in my case) which can be quite expensive for big projects.
IMHO, this request would break a key bit of compatibility git has with build engines that depend on timestamps. The request would cause the IDE to have false negatives during builds because the files that changed are not recognized as changing. A typical approach to do what you are requesting, where make is involved, is to use the --touch option after the stash pop to bring objects up to date - not a great plan in C++ as you can get into signature mismatches that way. Nonetheless, could you not do something like that in MSVC?
--Randall
next prev parent reply other threads:[~2023-03-21 21:00 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 [this message]
2023-03-22 11:03 ` Ridil culous
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='000a01d95c38$0acfba10$206f2e30$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=reallyridilculous@gmail.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).