From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: "Bill Lear" <rael@zopyra.com>,
"Karl Hasselström" <kha@treskal.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: Git checkout preserve timestamp?
Date: Mon, 5 Mar 2007 16:01:45 +0000 [thread overview]
Message-ID: <200703051601.49370.andyparkins@gmail.com> (raw)
In-Reply-To: <17900.11612.872928.633406@lisa.zopyra.com>
On Monday 2007 March 05 14:46, Bill Lear wrote:
> All very wrong if you ignore what I wrote as part of my original note:
> keep compilation products separated by branch name, not in the same
I realise why it's causing you troubles. However, I was hoping that that
little example shows why it can never be right to use the timestamp out of
the repository.
> place. This is essential to my request: without it, it is indeed very
> wrong. We currently separate out by compiler, options, machine
> architecture, and adding the branch to that is trivial.
I'm afraid that the unnecessary recompile is just a by-product of that
organisation. I still say that git is correct to touch the file dates.
[blatent plug]: perhaps my poorman's submodule support will get you by until
real submodule support is implemented?
http://lists.zerezo.com/git/msg334639.html
I doubt it though - as you would probably want automatic checkout in your
situation.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-03-05 16:02 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 21:36 Git checkout preserve timestamp? Bill Lear
2007-03-01 21:48 ` Alex Riesen
2007-03-01 22:13 ` Johannes Schindelin
2007-03-01 22:25 ` Linus Torvalds
2007-03-01 22:32 ` Johannes Schindelin
2007-03-02 9:14 ` Karl Hasselström
2007-03-02 13:24 ` Bill Lear
2007-03-02 15:01 ` Bart Trojanowski
2007-03-02 15:18 ` Johannes Schindelin
2007-03-02 16:21 ` Karl Hasselström
2007-03-02 19:21 ` Johannes Schindelin
2007-03-05 7:23 ` Karl Hasselström
2007-03-05 11:32 ` Johannes Schindelin
2007-03-05 12:28 ` Karl Hasselström
2007-03-05 19:04 ` Bill Lear
2007-03-05 19:16 ` Johannes Schindelin
2007-03-05 19:59 ` Bill Lear
2007-03-05 20:44 ` Johannes Schindelin
2007-03-05 21:42 ` Bill Lear
2007-03-05 21:50 ` Linus Torvalds
2007-03-05 22:03 ` Matthieu Moy
2007-03-05 22:25 ` Bill Lear
2007-03-05 22:37 ` Linus Torvalds
2007-03-05 23:20 ` Bill Lear
2007-03-05 23:32 ` Johannes Schindelin
2007-03-05 23:38 ` Bill Lear
2007-03-05 23:50 ` Johannes Schindelin
2007-03-06 0:06 ` Michael Poole
2007-03-06 0:20 ` Johannes Schindelin
2007-03-06 0:37 ` Michael Poole
2007-03-06 1:40 ` Johannes Schindelin
2007-03-06 0:32 ` Junio C Hamano
2007-03-06 18:39 ` Sergio Callegari
[not found] ` <7vo dn7w6rz.fsf@assigned-by-dhcp.cox.net>
2007-03-06 1:21 ` Jakub Narebski
2007-03-06 0:24 ` Bill Lear
2007-03-06 1:34 ` Johannes Schindelin
2007-03-06 1:59 ` Bill Lear
2007-03-06 0:06 ` Martin Langhoff
2007-03-06 0:21 ` Theodore Tso
2007-03-05 22:39 ` Matthieu Moy
2007-03-05 22:56 ` Johannes Schindelin
2007-03-05 23:27 ` Bill Lear
2007-03-05 22:02 ` Johannes Schindelin
2007-03-05 22:29 ` Bill Lear
2007-03-05 12:13 ` Andy Parkins
2007-03-05 12:33 ` Karl Hasselström
2007-03-05 13:19 ` Andy Parkins
2007-03-05 14:53 ` Karl Hasselström
2007-03-05 14:46 ` Bill Lear
2007-03-05 16:01 ` Andy Parkins [this message]
2007-03-05 16:28 ` Bill Lear
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=200703051601.49370.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=rael@zopyra.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.