git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Andrei Faber <andrei.faber@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git gui produces series of commits with exactly the same time
Date: Wed, 29 Jun 2016 13:45:09 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1606291344400.12947@virtualbox> (raw)
In-Reply-To: <37a71a23-ded6-9d48-a873-a05f33e802bd@gmail.com>

Hi Andrei,

On Wed, 29 Jun 2016, Andrei Faber wrote:

> I've noticed that git history contains series of commits with exactly
> the same time, despite the real commit time of these commits was
> different. All these commit were made using the git gui tool. I'm the
> only developer in this project.

Is it possible that you played games with your GIT_AUTHOR_DATE environment
variable?

Ciao,
Johannes

  reply	other threads:[~2016-06-29 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  8:12 git gui produces series of commits with exactly the same time Andrei Faber
2016-06-29 11:45 ` Johannes Schindelin [this message]
2016-06-29 11:51   ` Andrei Faber
2016-06-30  5:59   ` Andrei Faber

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=alpine.DEB.2.20.1606291344400.12947@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=andrei.faber@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).