git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Toby Corkindale <toby.corkindale@rea-group.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: diff/Checking out by date specification
Date: Mon, 30 Jun 2008 01:26:12 -0400	[thread overview]
Message-ID: <20080630052612.GA22699@sigill.intra.peff.net> (raw)
In-Reply-To: <20080630052105.GA21954@sigill.intra.peff.net>

On Mon, Jun 30, 2008 at 01:21:05AM -0400, Jeff King wrote:

> Depending on what you want to do, that may be enough. But more likely,
> you are interested in the actual shape of history, so looking at the
> individual commits with something like "gitk --since=2008-01-01
> --until=2008-01-08" is probably going to be more instructive.

Side note: what you may have _really_ wanted was "what is the difference
between what was in Junio's 'master' branch on those dates". I.e.,
looking at the sequence of states at the tip of some "official" git
repo.

In that case, you could get the answer you want by looking in Junio's
reflog. However, that information is not generally available through
git. There is no support for downloading reflogs, and most people don't
have reflogs enabled on their published bare repos. If Junio enabled
reflogs on pushing to his bare repo, then you could manually download
them into your .git/logs/ hierarchy and pretend that that was your
history of your refs.

-Peff

      reply	other threads:[~2008-06-30  5:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30  2:24 diff/Checking out by date specification Toby Corkindale
2008-06-30  3:27 ` Jeff King
2008-06-30  4:38   ` Toby Corkindale
2008-06-30  5:09     ` Daniel Barkalow
2008-06-30  5:21     ` Jeff King
2008-06-30  5:26       ` Jeff King [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=20080630052612.GA22699@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=toby.corkindale@rea-group.com \
    /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).