git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Geoff Russell" <geoffrey.russell@gmail.com>
To: "Jeff King" <peff@peff.net>, git@vger.kernel.org
Subject: Re: reflog/show question
Date: Tue, 29 Apr 2008 11:17:09 +0930	[thread overview]
Message-ID: <93c3eada0804281847q267611aeke51b482cfbe100d6@mail.gmail.com> (raw)
In-Reply-To: <20080428092410.GD16153@sigill.intra.peff.net>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

On Mon, Apr 28, 2008 at 6:54 PM, Jeff King <peff@peff.net> wrote:
> On Mon, Apr 28, 2008 at 11:29:17AM +0930, Geoff Russell wrote:
>
>  >      git show HEAD@{"3 minutes ago"}
>  >
>  > works as I expect, but
>  >
>  >      git show HEAD@{"3 minutes ago"}:data/node/node.data
>  >
>  > gives me a message:
>  >
>  >        warning: Log for 'HEAD' only goes back to Mon, 28 Apr 2008
>  > 10:18:37 +0930.
>  >
>  > [...]
>
> > I'm using 1.5.4.rc4
>
>  I can't reproduce here, using the current master or v1.5.4-rc4. If I
>  have a matching reflog, both work. And if I choose a much older time
>  (say, "1.year.ago"), then both fail. What are the entries in your
>  reflog (.git/logs/HEAD)?

I think its something to do with the filename and my commit comments.
The command
works as expected on other files.  The HEAD file is attached.

Geoff

>
>  -Peff
>



-- 
6 Fifth Ave,
St Morris, S.A. 5068
Australia
Ph: 041 8805 184 / 08 8332 5069

[-- Attachment #2: HEAD --]
[-- Type: application/octet-stream, Size: 3317 bytes --]

0000000000000000000000000000000000000000 73387f4abc3f55ba93f9379d9359c5a03a516a66 MATRICS Software <matrics@faith.localdomain> 1209432646 +0930	commit (initial): createDataset newds1
73387f4abc3f55ba93f9379d9359c5a03a516a66 f13469b805a05cef213e3ca8b030e8314d196acc MATRICS Software <matrics@faith.localdomain> 1209432648 +0930	commit: setProperties
f13469b805a05cef213e3ca8b030e8314d196acc fe61eeaa85c8ec68935224bae99528fdcfc87352 MATRICS Software <matrics@faith.localdomain> 1209432659 +0930	commit: update .matrics.restrict
fe61eeaa85c8ec68935224bae99528fdcfc87352 7b0783a2f99131a1a759d16494f91889fe23e726 MATRICS Software <matrics@faith.localdomain> 1209432662 +0930	commit: new node.db
7b0783a2f99131a1a759d16494f91889fe23e726 2124da80643760e9cb65cbeea1678f6f65f6a603 MATRICS Software <matrics@faith.localdomain> 1209432665 +0930	commit: new node.newds1
2124da80643760e9cb65cbeea1678f6f65f6a603 4167fcad224941322c4a15e813ac4fdd702fa6ff MATRICS Software <matrics@faith.localdomain> 1209432666 +0930	commit: new node.delnewds1
4167fcad224941322c4a15e813ac4fdd702fa6ff b3d1ca03a6ede31ac7f7d4ea264aba6e17ca49bb MATRICS Software <matrics@faith.localdomain> 1209432667 +0930	commit: delf node.delnewds1
b3d1ca03a6ede31ac7f7d4ea264aba6e17ca49bb d6b727f0a54f64511126715d0f328261391ef60a MATRICS Software <matrics@faith.localdomain> 1209432671 +0930	commit: user=geoff,file=node.newds1,program=putf,cwd=/usr/local/AusTop/AuPrograms/AuServer,time=1209432671,sourceds=newds1
d6b727f0a54f64511126715d0f328261391ef60a f9975f6cc061350ab3d1d1b4947a218b0dfb8b23 MATRICS Software <matrics@faith.localdomain> 1209432674 +0930	commit: recvf node.newds1
f9975f6cc061350ab3d1d1b4947a218b0dfb8b23 8bbd74b28dbb0b350e699d661c748084e08edf3e MATRICS Software <matrics@faith.localdomain> 1209432686 +0930	commit: user=geoff,file=node.newds1,program=putf,cwd=/usr/local/AusTop/AuPrograms/AuServer,time=1209432685,sourceds=newds1
8bbd74b28dbb0b350e699d661c748084e08edf3e 1b83468bf234455040a270392992077bd0d07b01 MATRICS Software <matrics@faith.localdomain> 1209432689 +0930	commit: geoff resetting dataset 2124da80643760e9cb65cbeea1678f6f65f6a603
1b83468bf234455040a270392992077bd0d07b01 d2356b1ce02bbcbf24e1e7951f4fa00d5b58d4a0 MATRICS Software <matrics@faith.localdomain> 1209432690 +0930	commit: geoff resetting dataset HEAD@'{1}'
d2356b1ce02bbcbf24e1e7951f4fa00d5b58d4a0 f0265c2bbdefa52cd830bd0e9624eb7d720eed12 MATRICS Software <matrics@faith.localdomain> 1209432692 +0930	commit: copyf node.newds1 node.copynewds1
f0265c2bbdefa52cd830bd0e9624eb7d720eed12 bfe7094f4bd3b3f9ff33950c484b3b44e0d9b5e5 MATRICS Software <matrics@faith.localdomain> 1209432695 +0930	commit: delf node.copynewds1
bfe7094f4bd3b3f9ff33950c484b3b44e0d9b5e5 40c2c72852419f1c2220903ee977ea3e06338926 Geoff Russell <geoffrey.russell@gmail.com> 1209432997 +0930	commit: modify it
40c2c72852419f1c2220903ee977ea3e06338926 69edafd8371ed8613cf87736b69e3184f974cd74 Geoff Russell <geoffrey.russell@gmail.com> 1209433118 +0930	commit: add stuff
69edafd8371ed8613cf87736b69e3184f974cd74 8d4e7aa2303982da5dd1dff60b67e924098323b4 Geoff Russell <geoffrey.russell@gmail.com> 1209433220 +0930	commit: new file: data/node/xxx
8d4e7aa2303982da5dd1dff60b67e924098323b4 efe0f90772d84c808a228c1c785565a34b5b2c82 Geoff Russell <geoffrey.russell@gmail.com> 1209433250 +0930	commit: Okay

  reply	other threads:[~2008-04-29  1:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28  1:59 reflog/show question Geoff Russell
2008-04-28  9:24 ` Jeff King
2008-04-29  1:47   ` Geoff Russell [this message]
2008-04-29 20:12     ` Jeff King
2008-04-29 22:06       ` Geoff Russell
2008-04-29 23:07         ` Jeff King
2008-04-30  0:12           ` Geoff Russell
2008-04-30  0:26             ` Geoff Russell
2008-05-01  0:15               ` Geoff Russell
2008-05-01 13:53                 ` Jeff King
2008-05-02  2:21                   ` Geoff Russell

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=93c3eada0804281847q267611aeke51b482cfbe100d6@mail.gmail.com \
    --to=geoffrey.russell@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).