git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dhruva <dhruvakm@gmail.com>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org
Subject: Re: timestamps not git-cloned
Date: Fri, 28 Nov 2008 08:38:06 +0530	[thread overview]
Message-ID: <e3f230850811271908g1be6b3f9t3e678081088de06b@mail.gmail.com> (raw)
In-Reply-To: <87ej0wwptn.fsf@jidanni.org>

Hi,

On Fri, Nov 28, 2008 at 7:54 AM,  <jidanni@jidanni.org> wrote:
> 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 do not think there is an VCS that records timestamps. Only file
contents are tracked. Also, if you clone from systems across time
zones, what time do you expect to set on the files. IMO, it is not
practical to track timestamps.
 Are you concerned of 'make' doing a complete build when you switch
branches? I guess it makes sense only in that scenario. I wish 'make'
had some feature to track changes instead of timestamps alone...

-dhruva

-- 
Contents reflect my personal views only!

  reply	other threads:[~2008-11-28  3:10 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 [this message]
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
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=e3f230850811271908g1be6b3f9t3e678081088de06b@mail.gmail.com \
    --to=dhruvakm@gmail.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).