From: Michael Horowitz <michael.horowitz@ieee.org>
To: git <git@vger.kernel.org>
Subject: git-p4 and keyword substitution
Date: Fri, 6 May 2011 13:26:18 -0400 [thread overview]
Message-ID: <BANLkTinLW3Ty4n1ODKU-N000q7qQUoSDTQ@mail.gmail.com> (raw)
All,
I was wondering if there is a way to deal with this issue...
It seems that git removes the keyword substitutions from Perforce.
This is fine, except for the fact that it does not remove them from
the p4 client shadow. So, this causes git-p4 submit to fail whenever
it either deletes a file with keywords (since the file it is deleting
has the keywords and doesn't match) or lines close to the keywords
change, such that applying the patch doesn't work.
A Google search turned up a thread from a few years ago where someone
submitted a patch to make removing the keyword substitutions optional,
but I guess that patch never got accepted, at least not that I can
see.
Is there any other way of dealing with this?
Thanks,
Mike
next reply other threads:[~2011-05-06 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 17:26 Michael Horowitz [this message]
2011-05-06 19:29 ` git-p4 and keyword substitution Luke Diamand
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=BANLkTinLW3Ty4n1ODKU-N000q7qQUoSDTQ@mail.gmail.com \
--to=michael.horowitz@ieee.org \
--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;
as well as URLs for NNTP newsgroup(s).