From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jan Hudec <bulb@ucw.cz>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: mtimes of working files
Date: Thu, 12 Jul 2007 08:57:51 +0100 [thread overview]
Message-ID: <200707120857.53090.andyparkins@gmail.com> (raw)
In-Reply-To: <20070711202615.GE3069@efreet.light.src>
On Wednesday 2007 July 11, Jan Hudec wrote:
> I first thought the idea had something to do with make, but it will
> actually promptly break most build tools, because change to earlier version
> is a change too, but they wouldn't detect it.
I've found git's mtime setting to be the best where make is concerned so I
would hate to see it changed. Even when switching branches or rebasing or
whatever, only the changed files get rebuilt. The only time you get an
unnecessary rebuild is if you do
git checkout branch1
git checkout branch2
git checkout branch1
But we can hardly expect git to be responsible for that.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-07-12 7:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:08 mtimes of working files Yakov Lerner
2007-07-11 18:05 ` Johannes Schindelin
2007-07-11 18:36 ` Yakov Lerner
2007-07-11 18:42 ` Johannes Schindelin
2007-07-11 20:26 ` Jan Hudec
2007-07-12 7:57 ` Andy Parkins [this message]
2007-07-12 17:27 ` David Woodhouse
2007-07-13 0:37 ` Theodore Tso
2007-07-13 23:00 ` David Woodhouse
2007-07-13 23:18 ` Linus Torvalds
2007-07-13 23:46 ` David Woodhouse
2007-07-14 0:10 ` Linus Torvalds
2007-07-14 0:36 ` David Woodhouse
2007-07-14 0:44 ` J. Bruce Fields
2007-07-14 0:49 ` David Woodhouse
2007-07-14 1:29 ` Jakub Narebski
2007-07-14 13:23 ` Robin Rosenberg
2007-07-14 13:09 ` Julian Phillips
2007-07-14 22:22 ` Jan Hudec
2007-07-14 22:36 ` Julian Phillips
2007-07-15 1:46 ` Daniel Barkalow
2007-07-12 6:26 ` Eric Wong
2007-07-12 13:05 ` Randal L. Schwartz
2007-07-12 18:25 ` Eric Wong
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=200707120857.53090.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bulb@ucw.cz \
--cc=git@vger.kernel.org \
/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).