From: Elijah Newren <newren@gmail.com>
To: layer <layer@known.net>
Cc: git@vger.kernel.org
Subject: Re: need help with git show :1:...
Date: Wed, 8 Apr 2009 11:58:45 -0600 [thread overview]
Message-ID: <51419b2c0904081058p7d5a56c3j6aa5cebb0188ad43@mail.gmail.com> (raw)
In-Reply-To: <6838.1239212486@relay.known.net>
On Wed, Apr 8, 2009 at 11:41 AM, layer <layer@known.net> wrote:
> I remember this working for me in the not too distant past.
> I'm using git version 1.6.1.3. Perhaps it was an older version of git
> when it worked for me.
>
> quadra% ls -l src/c/sock.c
> -rw-r--r-- 1 layer fi 57909 Mar 9 13:32 src/c/sock.c
> quadra% git show :2:src/c/sock.c
> fatal: ambiguous argument ':2:src/c/sock.c': unknown revision or path not in the working tree.
> Use '--' to separate paths from revisions
> quadra% git show :1:c/sock.c
> fatal: ambiguous argument ':1:c/sock.c': unknown revision or path not in the working tree.
> Use '--' to separate paths from revisions
> quadra% git show :1:sock.c
> fatal: ambiguous argument ':1:sock.c': unknown revision or path not in the working tree.
> Use '--' to separate paths from revisions
> quadra% git show :1:/src/c/sock.c
> fatal: ambiguous argument ':1:/src/c/sock.c': unknown revision or path not in the working tree.
> Use '--' to separate paths from revisions
Does the file have conflicts? Try
$ git ls-files -s src/c/sock.c
and report what the output is.
If it doesn't have conflicts, but the file is tracked by git, using
stage 0 should work:
$ git show :0:src/c/sock.c
next prev parent reply other threads:[~2009-04-08 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 17:41 need help with git show :1: layer
2009-04-08 17:58 ` Elijah Newren [this message]
2009-04-08 18:02 ` layer
2009-04-08 18:07 ` Elijah Newren
2009-04-08 18:10 ` layer
2009-04-08 18:25 ` Elijah Newren
2009-04-08 18:35 ` layer
2009-04-08 18:38 ` Elijah Newren
-- strict thread matches above, loose matches on Subject: below --
2009-04-08 17:57 layer
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=51419b2c0904081058p7d5a56c3j6aa5cebb0188ad43@mail.gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=layer@known.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).