From: Junio C Hamano <junkio@cox.net>
To: Jeff Carr <jcarr@linuxmachines.com>
Cc: git@vger.kernel.org
Subject: Re: git-ls-new-files & make patch, pull, etc.
Date: Thu, 08 Sep 2005 20:19:46 -0700 [thread overview]
Message-ID: <7v64tbrkq5.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 4320B8D7.7070004@linuxmachines.com
In my opinion, setting the file timestamp to the commit time (or
any other time other than the time of checkout) tends to screw
you up more than help you.
Suppose you have the latest checked out in your working tree,
you build and test, and find regressions. You'd want to check
out from an older commit, rebuild and make sure things used to
work correctly. If the checkout used the timestamp of the older
commit, however, all the things you built from the latest would
have timestamps newer than the source, so you would end up
always having to run "make clean" before rebuilding.
next prev parent reply other threads:[~2005-09-09 3:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 2:07 git-ls-new-files & make patch, pull, etc Jeff Carr
2005-08-23 5:15 ` Junio C Hamano
2005-09-06 20:42 ` Jeff Carr
2005-09-06 21:08 ` Junio C Hamano
2005-09-08 22:19 ` Jeff Carr
2005-09-09 3:19 ` Junio C Hamano [this message]
2005-08-23 6:48 ` Johannes Schindelin
2005-09-06 19:06 ` Jeff Carr
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=7v64tbrkq5.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jcarr@linuxmachines.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).