git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derek Mahar <derek.mahar@gmail.com>
To: git@vger.kernel.org
Subject: git-svn and incorrect working copy file timestamps?
Date: Thu, 19 Mar 2009 12:54:12 -0700 (PDT)	[thread overview]
Message-ID: <1237492452300-2505059.post@n2.nabble.com> (raw)


Should "git svn" not preserve the file timestamps of the original commit tree
in the working copy?  Using Git 1.6.2.1, built from source, I find that "git
svn clone" sets the file timestamps in the working copy to the current date. 
I expected the timestamps to match those of the tree as it was originally
committed.  I get this result using both Cygwin and Crunchbang Linux 8.10.02
(an Ubuntu derivative).

Derek
-- 
View this message in context: http://n2.nabble.com/git-svn-and-incorrect-working-copy-file-timestamps--tp2505059p2505059.html
Sent from the git mailing list archive at Nabble.com.

             reply	other threads:[~2009-03-19 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 19:54 Derek Mahar [this message]
2009-03-19 21:31 ` git-svn and incorrect working copy file timestamps? Derek Mahar
  -- strict thread matches above, loose matches on Subject: below --
2009-03-19 23:02 Guido Ostkamp

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=1237492452300-2505059.post@n2.nabble.com \
    --to=derek.mahar@gmail.com \
    --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 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).