From: Mikael Magnusson <mikachu@gmail.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: git branches and compilation
Date: Mon, 17 Jun 2013 12:57:35 +0200 [thread overview]
Message-ID: <CAHYJk3Rgbd3oW+VfAnAiDG4y9AssKoc5qFTQpCV=HZEmLFVi_A@mail.gmail.com> (raw)
In-Reply-To: <130615124610.ZM12323@torch.brasslantern.com>
On 15 June 2013 21:46, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Saturday, May 18, 2013, Phil Pennock wrote:
>
>> On 2013-05-18 at 16:24 -0700, Bart Schaefer wrote:
>> > (One of the few things I'm finding annoying about git is that
>> > a cloned repository doesn't preserve file timestamps.)
>>
>> There's a post-checkout hook [...]
>
> Having been annoyed a couple of times by things not recompiling when a
> different branch is checked out (especially the texinfo inputs in Doc/,
> leading to reams of bad node errors when doing "make info") I dug into
> this a bit further and found "metastore".
>
> http://david.hardeman.nu/software.php
>
> It's available as a Debian package and seems so far to do what I want,
> although I haven't really been able to test it thoroughly because no one
> else has pushed anything in the past couple of days.
I don't quite understand the purpose... When you change branches you want
the source files to have an updated mtime, otherwise they will not be newer
than the build files of the previously checked out branch and make will not
rebuild. So what git does is what you usually want for source code -> "the
files on disk changed so rebuild". How does setting the timestamps older
help?
--
Mikael Magnusson
next prev parent reply other threads:[~2013-06-17 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 19:46 Bart Schaefer
2013-06-17 10:57 ` Mikael Magnusson [this message]
2013-06-17 17:04 ` Bart Schaefer
2013-07-24 14:25 ` Richard Hartmann
2013-07-25 18:53 ` Bart Schaefer
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='CAHYJk3Rgbd3oW+VfAnAiDG4y9AssKoc5qFTQpCV=HZEmLFVi_A@mail.gmail.com' \
--to=mikachu@gmail.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).