git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Rick Liu" <rickliu@broadcom.com>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: standarize mtime when git checkout
Date: Tue, 9 Jul 2013 15:45:52 +0000	[thread overview]
Message-ID: <7D0754FFADBD2D4785C1D233C497C47B209B07D1@SJEXCHMB06.corp.ad.broadcom.com> (raw)
In-Reply-To: <51DB8966.2060308@lsrfire.ath.cx>

Thanks René~
I'll use "git archive" command to create the tarball.

Rick

-----Original Message-----
From: René Scharfe [mailto:rene.scharfe@lsrfire.ath.cx] 
Sent: Monday, July 08, 2013 8:54 PM
To: Rick Liu
Cc: git@vger.kernel.org
Subject: Re: standarize mtime when git checkout

Am 08.07.2013 23:39, schrieb Rick Liu:
> Hi,
>
> Currently when doing "git checkout" (either for a branch or a tag),
> if the file doesn't exist before,
> the file will be created using current datetime.
>
> This causes problem while trying to tar the git repository source files (excluding .git folder).
> The tar binary can be different
> even all of file contents are the same (eg. from the same GIT commit)
> because the mtime for the files might be different due to different "git checkout" time.
>
> eg:
> User A checkout the commit at time A and then tarball the folder.
> User B checkout the same commit as time B and then tarball the folder.
> The result tarball are binary different
> even though all of tarball contents are the same
> except the mtime for each file.
>
>
> Can we use GIT's commit time as the mtime for all of files/folders when we do "git checkout"?

That would break tools like make which rely on a files mtime to build 
them.  They wouldn't be able to detect switching between source file 
versions that are older than the latest build.

You can use "git archive" to create tar files in which all entries have 
their mtime set to the commit time.  Such archives only contain tracked 
(committed) files, though.  And different versions of git can create 
slightly different archives, but such changes have been rare.

René

      reply	other threads:[~2013-07-09 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 21:39 standarize mtime when git checkout Rick Liu
2013-07-08 22:03 ` Junio C Hamano
2013-07-09  3:54 ` René Scharfe
2013-07-09 15:45   ` Rick Liu [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7D0754FFADBD2D4785C1D233C497C47B209B07D1@SJEXCHMB06.corp.ad.broadcom.com \
    --to=rickliu@broadcom.com \
    --cc=git@vger.kernel.org \
    --cc=rene.scharfe@lsrfire.ath.cx \
    /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://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).