git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org
Subject: Re: timestamps not git-cloned
Date: Fri, 28 Nov 2008 13:58:24 +0100	[thread overview]
Message-ID: <200811281358.24592.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <87ej0wwptn.fsf@jidanni.org>

fredag 28 november 2008 03:24:04 skrev jidanni@jidanni.org:
> Gentlemen, it's my first git-clone,
> $ git-clone git://git.debian.org/git/pkg-fso/files.git
> and I'm disappointed to find the timestamps of the files created are
> all now and not the date of last edit. At least mention something
> about this on the git-clone man page.

I recommend every new Git user to scan the FAQ. It's not just clone,
it's in everything git does in the file system. There is a very good 
reason git behaves this way in general, although clone could be
exception, but then we would have a ton of questions about that
inconsistency.

-- robin

  parent reply	other threads:[~2008-11-28 12:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28  2:24 timestamps not git-cloned jidanni
2008-11-28  3:08 ` dhruva
2008-11-28  5:06   ` jidanni
2008-11-28  6:59     ` Daniel Barkalow
2008-11-29  8:54     ` Chris Frey
2008-11-29  9:22       ` Stephen R. van den Berg
2008-11-29 10:16         ` Thomas Rast
2008-11-30  0:48           ` jidanni
2008-12-01  9:09             ` Andreas Ericsson
2008-12-01 11:44               ` Jakub Narebski
2008-11-30  1:14           ` Sitaram Chamarty
2008-11-28  5:57   ` David Brown
2008-11-28 14:59   ` Peter Krefting
2008-11-28 11:51 ` Johannes Schindelin
2008-11-28 12:58 ` Robin Rosenberg [this message]
2008-11-28 13:20   ` Johannes Schindelin

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=200811281358.24592.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=jidanni@jidanni.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).