From: Roger Leigh <rleigh@codelibre.net>
To: git@vger.kernel.org
Subject: git and mtime
Date: Wed, 19 Nov 2008 11:37:52 +0000 [thread overview]
Message-ID: <20081119113752.GA13611@ravenclaw.codelibre.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
Hi folks,
I'm using git to store some generated files, as well as their sources.
(This is in the context of Debian package development, where entire
upstream release tarballs are injected into an upstream branch, with
Debian releases merging the upstream branch, and adding the Debian
packaging files.)
The upstream release tarballs contains files such as
- yacc/lex code, and the corresponding generated sources
- Docbook/XML code, and corresponding HTML/PDF documentation
These are provided by upstream so that end users don't need these tools
installed (particularly docbook, since the toolchain is so flaky on
different systems). However, the fact that git isn't storing the
mtime of the files confuses make, so it then tries to regenerate these
(already up-to-date) files, and fails in the process since the tools
aren't available.
Would it be possible for git to store the mtime of files in the tree?
This would make it possible to do this type of work in git, since it's
currently a bit random as to whether it works or not. This only
started when I upgraded to an amd64 architecture from powerpc32,
I guess it's maybe using high-resolution timestamps.
Thanks,
Roger
P.S. The repo I'm working on here is at
git://git.debian.org/git/collab-maint/gutenprint.git
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-11-19 12:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 11:37 Roger Leigh [this message]
2008-11-19 12:22 ` git and mtime Matthias Kestenholz
2008-11-20 8:38 ` Andreas Ericsson
2008-11-20 11:20 ` Roger Leigh
2008-11-20 12:48 ` Andreas Ericsson
2008-11-20 13:12 ` Andreas Ericsson
2008-11-19 12:31 ` Johannes Schindelin
2008-11-19 12:37 ` Arafangion
2008-11-19 14:54 ` Matthieu Moy
2008-11-20 8:39 ` Andreas Ericsson
2008-11-20 10:34 ` Johannes Schindelin
2008-11-20 10:53 ` Matthieu Moy
2008-11-19 13:29 ` Jakub Narebski
2008-11-19 16:18 ` Christian MICHON
2008-11-20 10:35 ` Johannes Schindelin
2008-11-20 11:27 ` Roger Leigh
2008-11-20 13:06 ` Andreas Ericsson
2008-11-20 14:15 ` Roger Leigh
2008-11-20 14:50 ` Andreas Ericsson
2008-11-20 15:19 ` Roger Leigh
2008-11-20 15:33 ` Kyle Moffett
2008-11-20 15:37 ` Andreas Ericsson
2008-11-20 18:36 ` Matthias Kestenholz
2008-11-20 13:11 ` Randal L. Schwartz
2008-11-20 13:40 ` Roger Leigh
2008-11-20 17:59 ` Daniel Barkalow
2008-11-20 19:24 ` Joey Hess
2008-11-20 13:21 ` martin f krafft
2008-11-20 13:35 ` Roger Leigh
2008-11-20 13:59 ` martin f krafft
2008-11-20 15:56 ` Samuel Tardieu
2008-11-20 14:07 ` Johannes Schindelin
2008-11-20 14:22 ` Roger Leigh
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=20081119113752.GA13611@ravenclaw.codelibre.net \
--to=rleigh@codelibre.net \
--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 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.