From: Matthias Kestenholz <mk@spinlock.ch>
To: Doug Reiland <dreiland@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to capture date/time of push vs. local commit?
Date: Thu, 08 May 2008 16:06:48 +0200 [thread overview]
Message-ID: <1210255608.6737.12.camel@futex> (raw)
In-Reply-To: <6844644e0805080648g72c4b767l4bcf48ade319bf77@mail.gmail.com>
Doug,
On Thu, 2008-05-08 at 09:48 -0400, Doug Reiland wrote:
> I have a main repository that folks clone and push to. Using git-log
> for example on the main repository can show some confusing (too me at
> least) date.
>
> For example, I clone. I make changes to my repository and commit on
> Monday. I don't push my changes to the main repository until
> Wednesday.
>
> git-log on main repository show changes made on Monday.
> This makes it hard to determine when folks really got stuff into the
> main repository.
>
> Is there way to change this so (in my example), I can determine those
> changes weren't in place until Wednesday? Something in configuration
> file or perhaps just a different option to git-log.
>
> Thanks in advance.
This is the nature of a distributed version control system. The
timestamps cannot be used to establish a ordering of commits.
If you have reflogs enabled on the server (see man git-reflog) the
information there can help you find out when the pushes have been made.
There is no mechanism to transfer these reflogs into your local
repository, since reflogs are always local to a single repository. If
you have access to the server, you can examine the reflogs there. (f.e.
using git log -g or git reflog)
--
http://spinlock.ch/blog/
prev parent reply other threads:[~2008-05-08 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 13:48 How to capture date/time of push vs. local commit? Doug Reiland
2008-05-08 13:57 ` Eric Hanchrow
2008-05-08 14:06 ` Matthias Kestenholz [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1210255608.6737.12.camel@futex \
--to=mk@spinlock.ch \
--cc=dreiland@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).