From: Kevin Daudt <me@ikke.info>
To: Andrew Wolfe <andrew@schemaczar.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: Git enhancement request - checkout (clone) set modified dates to commit date
Date: Sun, 22 Apr 2018 21:59:24 +0200 [thread overview]
Message-ID: <20180422195923.GA10082@alpha> (raw)
In-Reply-To: <1FCE6958-FC75-4A9B-88A3-05AE991815E4@schemaczar.com>
On Sun, Apr 22, 2018 at 03:01:10PM -0400, Andrew Wolfe wrote:
> Hi Brian,
>
> Not completely sure what you're saying. If the files on master are
> not changed, the changed files' commit timestamps will be older than
> the branch commit timestamps.
>
> However, if I check out master after committing to a branch, the
> modifications will necessarily disappear because they haven't been
> committed to master. Instead, under my proposal, each will get the
> timestamp of its prior commit.
>
Say I build the project while on a certain branch. Then I checkout a
different branch and build again. You would expect that the targets of
every source file that have changed are rebuilt.
When you would restore the timestamp back to the commit timestamp, the
timestamp will be older then the target, and make will not rebuild it,
leaving you with outdated build targets.
next prev parent reply other threads:[~2018-04-22 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 17:18 Git enhancement request - checkout (clone) set modified dates to commit date Andrew Wolfe
2018-04-22 18:09 ` brian m. carlson
2018-04-22 19:01 ` Andrew Wolfe
2018-04-22 19:59 ` Kevin Daudt [this message]
2018-04-23 0:23 ` Andrew Wolfe
2018-04-23 3:32 ` Jacob Keller
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=20180422195923.GA10082@alpha \
--to=me@ikke.info \
--cc=andrew@schemaczar.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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).