From: Bill Door <duanemurphy@mac.com>
To: git@vger.kernel.org
Subject: Re: git p4 diff-tree ambiguous argument error
Date: Fri, 11 Jul 2014 10:40:49 -0700 (PDT) [thread overview]
Message-ID: <1405100449405-7614882.post@n2.nabble.com> (raw)
In-Reply-To: <1405013428825-7614774.post@n2.nabble.com>
More data points. I have reproduced the problem on
$ git --version
git version 1.8.5.2 (Apple Git-48)
$ python --version
Python 2.7.5
$ uname -a
Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014;
root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
However, it the command is used on a new empty repository, there is no
failure. Running a second time causes the failure.
Thanks for any help you can offer in tracking down this problem!
--
View this message in context: http://git.661346.n2.nabble.com/git-p4-diff-tree-ambiguous-argument-error-tp7614774p7614882.html
Sent from the git mailing list archive at Nabble.com.
prev parent reply other threads:[~2014-07-11 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 17:30 git p4 diff-tree ambiguous argument error Bill Door
2014-07-10 18:07 ` Luke Diamand
2014-07-10 18:08 ` Duane Murphy
2014-07-10 19:19 ` Duane Murphy
2014-07-12 18:10 ` Pete Wyckoff
2014-07-12 19:19 ` Duane Murphy
2014-07-11 17:40 ` Bill Door [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=1405100449405-7614882.post@n2.nabble.com \
--to=duanemurphy@mac.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.