From: Krzysztof Halasa <khc@pm.waw.pl>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Hard-linked trees with git?
Date: Wed, 19 Oct 2005 13:23:52 +0200 [thread overview]
Message-ID: <m3irvt21iv.fsf@defiant.localdomain> (raw)
In-Reply-To: <7vpsq2pmyl.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Tue, 18 Oct 2005 13:52:18 -0700")
Junio C Hamano <junkio@cox.net> writes:
>> Or: is it possible to have some constant file timestamps, so that
>> changing the HEAD to something and returning to the old HEAD
>> (say, with hard resets) restores the old timestamps?
>
> That would screw up 'make'.
Not if the old timestamps matched the old files and if you make sure
you don't mix different branches with one object tree (i.e., you always
switch to correct HEAD before building).
--
Krzysztof Halasa
prev parent reply other threads:[~2005-10-19 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 20:18 Hard-linked trees with git? Krzysztof Halasa
2005-10-18 20:52 ` Junio C Hamano
2005-10-19 11:23 ` Krzysztof Halasa [this message]
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=m3irvt21iv.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).