From: "Benjamin Sergeant" <bsergean@gmail.com>
To: git@vger.kernel.org
Subject: [git-p4] Cannot submit to perforce
Date: Tue, 8 Jul 2008 16:30:44 -0700 [thread overview]
Message-ID: <1621f9fa0807081630o5308d035o49a2b2dd60cceffe@mail.gmail.com> (raw)
With today's git:
I'm trying to reproduce the git commands git-p4 execute.
$ git branch -r
p4/HEAD
p4/master
$ git diff-tree -r
"0a41bb5b8387517ca5c45c56544e978b2f82f021^".."0a41bb5b8387517ca5c45c56544e978b2f82f021"
:000000 100755 0000000000000000000000000000000000000000
67406438a99bb212502eb3f3581527f046a96964 A
r3d/Viewer/qtgui/tools/buildrss.py
...
...
...
$ git format-patch -k --stdout
"0a41bb5b8387517ca5c45c56544e978b2f82f021^".."0a41bb5b8387517ca5c45c56544e978b2f82f021"
| git apply --check -
<stdin>:225: trailing whitespace.
#
<stdin>:233: trailing whitespace.
#
<stdin>:273: trailing whitespace.
<stdin>:275: trailing whitespace.
<stdin>:295: trailing whitespace.
error: r3d/Viewer/qtgui/tools/buildrss.py: already exists in working directory
...
...
...
For me the "already exists in working directory" means we are not in
the right branch, and that we are trying to apply the same commit on
the master branch ?
If I issue git-p4 submit I have basically the same output, I say
"[s]kip this patch" and it ends with:
"""
Some files in your working directory are modified and different than
what is in your index. You can use git update-index <filename> to
bring the index up-to-date or stash away all your changes with git
stash.
"""
If I retry git-p4 submit with doing the stash, sometimes the perforce
submit goes fine, sometimes not... ???
Thanks for any help,
Benjamin.
reply other threads:[~2008-07-08 23:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1621f9fa0807081630o5308d035o49a2b2dd60cceffe@mail.gmail.com \
--to=bsergean@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